WHAT IS USER ACCEPTANCE TEST? HOW IT IS DIFFERENT FROM SYSTEM TESTING?.

 User acceptance and System Testing both types of tests are executed against the entire system/application. It's very possible many of the tests will overlap.  A system testing : is often executed by an independent QA team in a production-like environment. This may be the first time all of the components are tested together. This includes testing of every input in the application to check for desired out puts.  User acceptance : is a type of testing performed by the Client to certify the system with respect to the requirements that was agreed upon. This testing happens in the final phase of testing before moving the software application to Market or Production environment.  The main purpose of this testing is to validate the end to end business flow. It does NOT focus on the cosmetic errors, Spelling mistakes or System testing.  This testing is carried out in same production environment or separate testing environment with production like data setup. It is a kind of black box testing where two or more end users will be involved.

 Prerequisites of User Acceptance Testing: E ntry criteria for user acceptance testing: 1.Business requirements must be available. 2.Application code should be fully developed 3.Unit Testing, Integration Testing & System Testing Should be completed 4.No showstoppers, high, medium defects in system integration test phase - only cosmetic error are acceptable before UAT 5.Regression testing should be completed with no major defects all the reported defects should be fixed and tested before UAT 6.traceability matrix for all testing should be completed 7.UAT environment must be ready 8.sign off mail or communication from system testing team that the system is ready for UAT execution

 Who will perform : User /client  Why we need UAT : Once a software has undergone Unit, Integration and System testing the need of Acceptance Testing may seem redundant. But Acceptance Testing is required because  1) Developers code software based on requirements document which is their "own" understanding of the requirements and may not actually be what the client needs from the software.  2) Requirements changes during the course of the project may not be communicated effectively to the developers.  Where it will be performed : QA environment : If testing is performed in the production environment with the internal employees of the organization it is called ALPHA testing Production Environment :if The product is released to real-time environment to limited number of end users ahead of the time for their feed back that is called BETA testing. Irrespective of which environment it takes the process is more or less will be the same.

 Why: purpose of the UAT testing Is validation of business requirements. EX: if you take any websites like EXpedia or any other ticket booking sites When we performing UAT testing assuming us as a user we are not going to test whether this field is taking special characters or not, this field is working properly or not or the error messages or notifications are showing properly or not. That’s not the focus of this testing Because UAT testing comes after the system testing where all those basic issues were caught and fixed.  Entity: UAT is all about the testing the entity of the business. For example if you take Expedia or any other websites it is all about ticket booking for flights, rental cars, hotels etc. Make cancel Make confirm pay Make confirm cancel Make confirm Issue-Use UAT is all about testing the end to end business flow.

UAT is an Autonomous testing Project : which means it has its own Test Plan: system plan test scope Who will perform etc. Test Design : Acceptance criteria Test Cases sub set of system test suites, end to end in nature execution: result go or no go end decision. QA Team Involvement Assist : we will assist UAT team by providing the test cases, we would be the standby if needed we will train them on how to use the software we use, when we are on standby we will answer the question on what they will arise because they are fairly new to the application than we are. Total involvement: We will execute the test cases and give them the results. executing: after executing the test cases the result will consider to take the decision of going for production or not. Bugs: based on the severity of the bugs they will decide where to go for lease and fix the bugs separate release. Result interpretation/decision : important thing is final decision is always the UAT team it is never QA team.