Key Roles
Sales excutives are the ones usually targeted by this use case. To better understand why these personas are targeted by this use case, you need to know roughly what their responsibilities are.
A sales executive is responsible for driving revenue growth for a company by selling its products or services to potential customers. Their role involves various activities aimed at identifying prospects, building relationships, and closing deals.
Scenario
In Pricefx ➡️ Quoting, Sales persons and executives can see what are the target, floor and stretch margins and can make informed decisions when quoting to a client. Moreover, they can export the quote, set up contracts and much more.
In this use case, as a Sales executive, you want to make sure that the quoting process is working correctly and the created quote is exported to ERP.
To ensure that your user story is viable and can be correctly implemented, you need to clearly define the acceptance criteria used for testing the use case. In this situation, the acceptance criteria is:
☑️ My ToDo List contains correct information about your quotes
☑️ All parameters for the new quote were correctly entered
☑️ The quote was correctly submitted
☑️ The quote was correctly approved
☑️ The quote was correctly exported to pdf and the file contains the same data as the quote created in this test
☑️ The quote was correctly exported to ERP system
LEARN MORE: To learn about how the User Acceptance Test works and all the phases it encompasses as well as what you should and should not expect, click here.
Once you are familiar with what UAT entails, you can proceed and test your scenario. Keep in mind that this is a sample UAT script and that in most cases, acceptance test are highly tailored to the customer and their needs. This is why it is paramount that in the Preparation Sprints you take the time to clearly design your user stories, you make sure that all the data uploaded is of good quality and that the person assigned to test is familiar with the user story and Pricefx.
Good to know: See what happens in the Sprints and why your contribution is crucial to the project, here.
Good to know: Learn how to get your data ready and ensure that is of the best quality, here.
Good to know: Learn how to select the best person to test for validation, here.
Sample UAT
Below, is a sample UAT for Price Setting ➡️ Quoting. You will notice that this is an end to end test, meaning a reliable way to guarantee that the application performs as expected and seamlessly handles data flow and mimics real-life scenarios error free. It also means that it encompasses several user stories that make up the use cases utilized to design the testing scenario in question.
Scenario details
The scenario we are looking at here is:
The Sales executive, in this scenario, wants to make sure that the quoting process is working correctly and the created quote is exported to ERP.
The expected result here is that the new quote is applied and visible in Quoting without errors or warnings and it can be seamlessly exported to the ERP.
User Acceptance Test Script: Quote process is working correctly and created Quote is exported to ERP
Dependency
-
Access to the partition
Pre - condition:
Ensure access to the Pricefx application as a Sales Executive by checking that you have the right permissions.
Test steps
-
Login to Pricefx as a Sales Account Manager
Action: Enter valid credentials and click on the Login button.
-
Check Home page "My ToDo List" - and verify all your Quotes which require your attention are displayed here
Action: Navigate to Pricefx home> My ToDo list and browse item(s) you are interested in
-
Open Quotes
Action: Navigate to Quotes screen (Quoting - Quotes).
-
Start creating a new quote
Action: Navigate to Quoting> Create a new quote. You can create it either from scratch or from an existing quote by duplicating it
-
Make sure the correct customer is selected in the Header screen and correct Items are selected in Items screen
Action: Click on the customer and items you are interested in
-
Make sure all parameters in the Quote are correctly selected
Action: You can use Guidance View if needed
-
Submit the quote and verify it needs approval from a manager
Action: Click submit from the ribbon or the paper plane icon
-
Login to Pricefx as a Sales Manager and display the correct LPG
Action: Click on Price Setting > Live Price Grid > selected test LPG set prior
-
Approve the quote created and submitted in this test
Action: Click on the check mark icon to approve
-
Export the Quote to pdf format and open the exported file
Action: Open the dropdown and select export to PDF
-
Check that approved quote was correctly exported to ERP
Action: Check that all approved items were correctly exported to ERP and that the new quote is visible there
Expected Results
Step 2 - Expected Result: My ToDo List contains correct information about your quotes after step 2
Steps 5, 6 - Expected Result: All parameters for the new quote were correctly entered after steps 5 and 6
Step 7 - Expected Result: The quote was correctly submitted after step 7
Step 9 - Expected Result: The quote was correctly approved after step 9
Step 10 - Expected Result: The quote was correctly exported to pdf after step 10 and the file contains the same data as the quote created in this test
Step 11 - Expected Result: The quote was correctly exported to ERP system after step 11
Validation
If the test was performed correctly and the application behaved as expected, the UAT is considered successful and validated as PASS.
If during testing there were errors, mistakes in data, or the application did not meet the expected results and criteria, then the test is considered as FAIL.
In latter situation, a comprehensive list of bugs and errors should be submitted for fixes and re-testing. Depending on the reported issues, the time until re-testing is possible may vary.
Bugs and errors
Any deviations or failures in the expected results should be reported as defects for further investigation and resolution.
Good to know: Learn how to report bugs in Pricefx, here.
Considerations
Some acceptance tests will take a few days, so make sure that you allocate the right amount of time as recommended. In this situation, the recommended man days is 5.
Remember that a designated person who is familiar with the user story and the acceptance criteria and is capable to identify errors should test.
Good to know: For more details on how to select the right person, click here.
Challenges and how to avoid them
UAT testing is a bit different from other QA activities because it involves not only tech specialists but also actual end users. It is important to involve QA professionals, business analysts, the project manager, and the development team to ensure a smooth process.
During UAT activities, just like any other stage of the development cycle, you might encounter some challenges. But do not worry, here are some ideas to help you stay prepared:
-
If poor planning is the issue, make sure to allocate enough time for UAT to avoid incomplete results.
-
Get the right testing environment otherwise a wrong environment can cause an array of issues. The UAT environment should be different from the one used for functional testing.
-
Inappropriate tester selection is another hurdle. Choose testers from the specific group that represents the main target audience of the feature/ scenario you are testing.
-
Ensure that testers receive proper training before conducting UAT to maximize its effectiveness as lack of training can hinder effective testing.
Pricefx offers a wide variety of trainings to help users get the most of the application. Check our catalog here.
-
Inefficient communication can be detrimental to the acceptance test. Establish a seamless communication process between teams to prevent gaps, misunderstandings, and delays.
By keeping these challenges and our guidelines in mind, you'll be able to carry out efficient and productive user acceptance testing.