Identifying and implementing effective automated tests in Naveo Hub
Hao, Katharine (2023)
2023
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2023120835327
https://urn.fi/URN:NBN:fi:amk-2023120835327
Tiivistelmä
Naveo Commerce is a company that specializes in grocery e-commerce software. Their product Naveo Hub is a retailer admin panel that includes route planning and fulfilment area management features. Due to the complexity of these features, it is time consuming to manually click through and ensure that the essential flows are working. Since few automated regression tests exist, the goal of the study was to identify and write tests that would best benefit the testing process of these features, reducing the manual testing time.
Research was conducted to determine what kind of tests would best balance the time spent to write them and the value they would bring. Through this research, it was decided that end-to-end Cypress tests would be the most beneficial, and they were written within three weeks. The PDCA cycle was used to improve the process. Although not everything could be included in the automated end-to-end tests written in Cypress, the main functionality was covered. While writing the tests, two bugs were fixed, and two improvements were made. The tests were run for five code changes in the following six months, reducing the manual testing time.
Research was conducted to determine what kind of tests would best balance the time spent to write them and the value they would bring. Through this research, it was decided that end-to-end Cypress tests would be the most beneficial, and they were written within three weeks. The PDCA cycle was used to improve the process. Although not everything could be included in the automated end-to-end tests written in Cypress, the main functionality was covered. While writing the tests, two bugs were fixed, and two improvements were made. The tests were run for five code changes in the following six months, reducing the manual testing time.