This article discusses the benefits of test automation in the field of quality assurance. It explains that test automation can be used during feature sprints to support development and after go-live to support regression testing. The article highlights key scenarios for using test automation, such as verifying key business cases and ensuring the seamless integration of functionalities. It also provides an overview of test automation at Pricefx, including the technology used and the scope of automation packages. Additionally, the article mentions the pros and cons of automated testing, emphasizing the benefits of faster testing, elimination of human errors, and fast issue detection in business critical functionalities. It also acknowledges the need for development and maintenance in test automation.

There are 2 ways how to use test automation on project:

• during Feature Sprints to support development

• after Go-Live to support regression testing after upgrades, change requests or bug fixes

Key scenarios for Test Automation

In projects featuring multiple phases, we prioritize the verification of key business cases. After each phase, test automation scripts examine previously developed and approved functionalities, ensuring their seamless integration with new developments. Post Go-Live, regular testing is eliminated, relying instead on nightly automation scripts to verify vital functionalities. This not only ensures efficiency but also facilitates prompt detection of issues after small changes or bug fixes. The scripts also prove invaluable after updates or upgrades, checking the application's performance after fixes done from COSA. Moreover, our commitment to user support extends to assisting with the training of new users on the Pricefx software. Leveraging Cypress, recorded videos demonstrate the application's usage, providing useful guidance to new users in Pricefx.

Test Automation Overview

At Pricefx we use http://Cypress.io , an open-source framework incurring no extra costs that ensures a cost-effective and efficient testing process. Tailoring the scope to the selected package and mutually agreed-upon use cases with our customers before embarking on test automation development, we make sure we are in alignment with specific project needs. Maintenance is integrated into our subscription model, ensuring ongoing support. The test automation development kicks off post UAT acceptance and wraps up post Go-Live, ensuring a smooth transition and comprehensive testing throughout the project lifecycle.

Check Points

Prior to test automation, the scope definition and thorough test data preparation must be the focal point of the process. This upfront effort ensures a smooth sailing for automation. It's worth noting that, during the detailed scope definition, we must consider any technical limitations that may arise, ensuring a realistic and feasible approach. This holistic approach not only assures efficiency but also injects a sense of clarity and precision into testing.

Check points examples:

• Correct calculation of selected parameters in LPG

• Checking selected parameters in PP tables

• Submitting Quotes/Rebates for selected business roles

• Expected values in Dashboard

• Correct values in Datamart

Scope of test automation packages

Open

Test Automation at a glance

Open

End-to-End Test Automation

In the next section we are looking at the end-to-end automated tests for the Pricefx solution. Such testing, as mentioned in the prior sections, is very useful especially for regression testing of existing functionality after new development or software upgrades. Moreover test automation reduces the time spent on manual regression testing while it increases the quality of software application  and user confidence in the solution.

Below is a video example – automatically recorded after test automation

Technology used

At Pricefx we rely on two pillars for testing:

Test Automation Pros and Cons

With testing automation, the benefits outweigh the disadvantages which are mainly focused on the limitations that occur.

The benefits include but are not limited to:

• Faster than manual testing

• Human errors eliminated

• Can be run automatically when needed (after deployment, every day, new version of pfx sw)

• Can be evaluated by the customer (test results are recorded)

• Repeats the same test without complaining

• Can help with fast issue detection in business critical functionalities

On the side of minuses, some of the things we are looking at are development and regular maintenance needs. Automation testing also relies on cooperation on various aspects (define scope, choose test scenarios, prepare test data). Just because it is automated, test automation does not mean no testers will be needed; some are still needed for maintenance, evaluation, automation of new tests. Finally, in this case the focus is only on Pricefx and the same test is repeated.

If the test fails, you will see this screen: