UAT Test Case Examples
The article provides a set of UAT (User Acceptance Testing) test case examples for the Pricefx application, a pricing management software. These test cases cover various functionalities such as creating new quotes and rebate agreements, verifying data in dashboards, recalculating margins and prices, and testing the workflow for quotes. The article outlines the steps to be followed in each test case and the expected results to be checked.
You can download the Excel file with these sample UAT cases, here.
Good to know: Lets outlines the criteria for creating UAT test cases for the Pricefx application:
Identification of test case, must be unique for every test case
The summary should be a brief description of what will be tested in the test case
The description should be detailed and include what will be tested, including detailed steps
The expected results should include a description of test result which should be observed after testing
The Pricefx Module identifies which module/ capability is tested in the test case
Pricefx Module Test Case Examples
Here is a sample of how this may look like. Please keep in mind this is merely a guideline for good practices and your testing sheet may very likely look differently, according to your requirements.
ID | Summary | Description | Expected Results | Pricefx Module |
---|---|---|---|---|
UAT_001 | Create a new quote for existing customer | Verify that a new quote can be created in Pricefx application and after it is created, it is correctly visible in CRM system. Use the following guidelines to test the scenario:
| The following results should be checked in this scenario:
| Quote configurator |
UAT_002 | Verify data in Revenue and margin Dashboard | Verify that the correct data is visible in Revenue and margin Dashboard. Use the following guidelines to test the scenario:
| The following results should be checked in this scenario:
| Dashboards |
UAT_003 | Verify LPG for country was correctly recalculated | Verify LPG was correctly recalculated after parameters were changed. Use the following guidelines to test the scenario:
| The following results should be checked in this scenario:
| Price builder |
UAT_004 | Verify "Price" was correctly calculated according to the correct formula | Verify Price calculation works correctly after parameters were changed. Use the following guidelines to test the scenario:
| The following results should be checked in this scenario:
| Price builder |
UAT_005 | Verify Final Price is correctly displayed when Override parameter was used for country was correctly recalculated | Verify Final Price was not calculated when Override parameter was set Use the following guidelines to test the scenario:
| The following results should be checked in this scenario:
| Price builder |
UAT_006 | Verify workflow for quotes works correctly | Verify that a quote created by Sales Manager needs to be approved by Country Manager. Use the following guidelines to test the scenario:
10. Verify the created quote is visible in CRM system as Approved | The following results should be checked in this scenario:
| Quote configurator |
UAT_007 | Verify correct data was uploaded to Datamart Sales Load | Verify correct data was uploaded to Datamart. Use the following guidelines to test the scenario:
| The following results should be checked in this scenario:
2.Data loaded to DM are correct according to CRM system after step 5 | Price analyzer |
UAT_008 | Create a new rebate agreement for existing customer | Verify that a new rebate agreement can be created in Pricefx application and after it is created, it is correctly visible in CRM system. Use the following guidelines to test the scenario:
| The following results should be checked in this scenario:
| Rebates |
Â