Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Understanding the importance of testing is essential both for using test cases properly but also for knowing how to apply them on projects.
When we discuss the testing methodology, there is a set of standard activities that must be considered. In the case of Pricefx, we divide them in 3 major sections: preparation and setup, Feature Sprints, and UAT. Each of these have specific steps that must be taken.
Preparation and Setup
Test plan preparation
User stories and acceptance criteria review from testing point of view
UAT process clarification with the customer if agreed
Integration and data testing
Feature Sprints
Create test cases for user stories
Test the solution according prepared test cases, document and report test results
Regression testing in later Feature Sprints
Investigate bugs reported by the customer
UAT and testing support for the customer if needed
Create a demo for the customer
UAT
Investigate bugs reported by the customer
Support the customer during UAT testing
...
Lastly, in the UAT stage, help the customer organize the user acceptance testing and make sure that the testers are trained in using X-Ray effectively.
How To - Test Cases
Testing is recommended as good practice in general before accepting software. However, for big projects, long term customers in particular need clear visibility when testing. To make sure that this is covered, at Pricefx we prefer to use JIRA, X-Ray, Cypress and occasionally Excel. These come in handy also for small projects and bug retesting.
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Find out more about each of these by checking out the links below. /wiki/spaces/CUST/pages/3379397455 |