Project 1 - V&V SW Analysis - I
User acceptance Testing:
User Acceptance Testing (UAT), also known as beta or end-user testing, is defined as testing the software by the user or client to determine whether it can be accepted or not. This is the final testing performed once the functional, system and regression testing are completed. The main purpose of this testing is to validate the software against the business requirements. This validation is carried out by the end-users who are familiar with the business requirements.
Process:
The easiest way to understand this process is to think of this as an autonomous testing project, which means, it will have the plan, design and the execution phases.
User Acceptance Test Planning:
The process is almost the same as with the regular test plan in the system phase. The most common approach followed in most of the projects is to plan for both system and UAT testing phases together. For more information on the UAT test plan along with a sample, please check out the attached test plan document’s UAT sections.
Test plan Conditions:
if(user long press the power button)
{
open the company logo at centre;
}
else if(user click the power button)
{
open the apps in grid;
}
else if(user power on the phone)
{
show phone icon in the first position at the bottom;
}
else if(user power on the phone)
{
shows Dictionary icon on the second position at the bottom;
}
else if(user click on phone icon)
{
contacts will appear in chronological order;
}
else if(user click on Dictionary icon)
{
search bar will appears at center;
}
else if(user long press power button)
{
displays "Good-Bye" and phone gets switched off;
}
else if(user phone font)
{
always in calibri with size of 12;
}
else if(user requirement touch responsive)
{
reflects on touch;
}
else (user requires no hard buttons)
{
touch screen sensitive;
}
Conclusion:
User Acceptance Testing is not about the pages, fields, or buttons. The underlying assumption even before this test begins is that all that basic stuff is tested and is working fine. God forbid, the users find a bug as basic as that – it is a piece of very bad news for the QA team.