Process Overview

Establish criteria: To 'accept' or 'not accept' needs to be defined from the beginning. Mutually agreed-upon requirements are usually decided in the beginning of the project as a gate before a client or customer accepts the new system.

Develop tests: Based on the acceptance criteria, tests are created ideally through collaboration between the customer, testers, and developers. However the customer is the primary owner of these tests. As the user stories pass acceptance criteria, the customer can be sure that the developers are progressing in the right direction. It's essential that user acceptance tests include both business logic and UI validation.

Execute tests: Users of the system perform these tests. The acceptance test suite is run against the supplied input data and the results obtained are compared with the expected results. If there is a correct match for every case, the test suite is said to pass. If not, the system may either be rejected or accepted based on previously set partial-pass conditions.

XBOSoft User Acceptance Testing Deliverables:

Test Plan: Outlining the testing strategy with entry/exit and pass/fail criteria, we work with you to derive from either your requirements specification or contract.

Acceptance Tests: Based on the Test plan and pass/fail criteria, we develop test scenarios and test cases with expected results that cover all aspects of the functionality of your system.

Test Log: All the test cases executed with expected versus actual results documented combined with defects and/or issues found. The issues/defects found during testing are discussed with the Project Team, Subject Matter Experts and Business Analysts and resolved as per the mutual consensus and to the satisfaction of the end users.

Sign Off: Upon successful completion of the User Acceptance Testing and resolution of the issues, we provide a recommendation on the acceptance of the system.