Don't confuse UAT with functional testing
The catch phrase to differentiate between UAT and functional testing is between the words, verification and validation. Some organisations may use the term Q.A testing instead functional testing.
The development of test cases, test conditions or test scenarios will be picked up from the functional requirements written by the business analysts. One functional requirement may have several test cases, there are a number of techniques a test analyst will utilize to construct these test cases. Lets look at a simple example, the functional requirement says the customer of a credit card application should be more then 18 years of age, straight from the onset this requirement has 3 possible test cases. Can you guess which 3? A test analyst may use boundary value analysis to determine the 3 test conditions and what data to use to test these conditions.
Whilst designing UA testing cases, in most instances there are scenarios that would overlap between QA and UA. Some overlap is necessary and is in-inevitable, however in many cases, it becomes repetitive exercise which in my opinion is a complete waste of effort. UA test cases should be focused on validation of the functionalities from user perspective. While the SIT would have already determined the end to end functionality. UA test case should test this from user perspective again. It should test the usability of the input and fields, testing of the pop-up or error messages. Does the function work with a tab or mouse click etc? and some additional exploratory testing would always bring benefit to the product quality.
The mind-set of a UA tester should be all things that would make the user experience seamless.
Hope these lessons helps you.
Happy testing.
Part-time database manager at Gotogardening.
7 年User acceptance testing (UAT) is the last phase of the software testing process. During UAT, actual software users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications. UAT is one of the final and critical software project procedures that must occur before newly developed software is rolled out to the market. UAT is also known as beta testing, application testing or end user testing. :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) And you can read more at https://www.techopedia.com/definition/3887/user-acceptance-testing-uat
CEO, KMC Ltd : MD, Citrus Global Ltd : Advisory Board/ CRO : Nimbal Ltd
9 年Very informative