(Professional Business Analyst Training

organisation)

Acceptance testing

Acceptance testing is a formal testing conducted to determine whether a system satisfies the business criteria.

This testing is done based on business requirements and needs.

It is performed by Client or end user with or without the assistance of testers.

Types of Acceptance Testing: Two categories of acceptance testing are:1) User Acceptance Testing (UAT)2) Business Acceptance Testing ( BAT)

User Acceptance testing: To ensure that the system satisfies the contractual acceptance criteria before being signed off as meeting user needs, User acceptance testing is done.

Business Acceptance testing:To ensure that the system will pass the acceptance test, the development organization of the supplier will conduct the Business acceptance testing. Objectives of Acceptance Testing.1) Confirms that the system meets the criteria.2) If there are any discrepancies, that can be identified.

Traditional BA (Waterfall) Agile BA

Requirements are documented in Use Cases,Business Requirements, Functional requirements, UI Specifications, Business Rules.

Requirements are documented in Epics, User Stories and optionally Business (or Essential) Use cases.

   

Focuses on completeness of requirement and spends time in ensuring the requirement is unambiguous and has all the details.

Focuses on understanding the problem and being the domain expert so that s/he can answer questions from the development team swiftly and decisively.

Focuses on getting a ‘sign off’ on the requirements.

Focuses on ensuring the requirements meet the currentbusiness needs, even if it requires updating them.

Often there is a wall between the BA/Business and the Development team.

Agile BA (Often called as Product Owner) is part of the team.

Tends to dictate solutions.Has to remain in the problem domain, leaving the development team ‘space’ to explore different solutions.

Long turnaround. Quick turnaround.

Focus on what the requirements document said. In other words, output (Artifact) is a well written thorough requirements document.

Focus on the functionality of the developed software. In other words, output (Artifact) is the software that meets thebusiness needs.

   

Execution of Acceptance Testing:Acceptance test cases are divided into sub groups1) Basic test cases2) Test cases that are complex to execute3) These test cases are executed in two phases4) Basic test cases from the basic test group are

executed in first phase.5) If the test results are satisfactory, then second

phase is executed where the complex test cases are taken up.

UAT ActivitiesSome steps when doing UAT1) User acceptance Test planning2) Designing UAT Test cases3) Approve acceptance test plan4) Executing Test cases5) Documentation of the defects found

during UAT6) Resolving the defects fixing.