acceptance testing

7
(Professional Business Analyst Training organisation) Acceptance testing

Upload: coepd

Post on 07-Nov-2015

2 views

Category:

Documents


1 download

DESCRIPTION

COEPD - Center of Excellence for Professional Development is a primarily a Business Analyst Training Institute in the IT industry of India head quartered at Hyderabad. COEPD is expert in Business Analyst Training in Hyderabad, Chennai, Pune , Mumbai & Vizag. We offer Business Analyst Training with affordable prices that fit your needs.COEPD conducts 4-day workshops throughout the year for all participants in various locations i.e. Hyderabad, Pune. The workshops are also conducted on Saturdays and Sundays for the convenience of working professionals. For More Details Please Contact us: Visit at http://www.coepd.com or http://www.facebook.com/BusinessAnalystTrainingCenter of Excellence for Professional Development3rd Floor, Sahithi Arcade, S R Nagar,Hyderabad 500 038, India. Ph# +91 9000155700, [email protected]

TRANSCRIPT

Slide 1

(Professional Business Analyst Training organisation)Acceptance testing

1

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: User Acceptance Testing (UAT)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 theBusiness acceptance testing.Objectives of Acceptance Testing.Confirms that the system meets the criteria.If there are any discrepancies, that can be identified.Traditional BA (Waterfall)Agile BARequirements are documented in Use Cases,BusinessRequirements, Functional requirements, UI Specifications, Business Rules.Requirements are documented in Epics, User Stories and optionallyBusiness(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 currentbusinessneeds, even if it requires updating them.Often there is a wall between theBA/Businessand the Development team.AgileBA(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 thebusinessneeds.

Execution of Acceptance Testing:Acceptance test cases are divided into sub groupsBasic test casesTest cases that are complex to execute These test cases are executed in two phases Basic test cases from the basic test group are executed in first phase.If the test results are satisfactory, then second phase is executed where the complex test cases are taken up.

UAT ActivitiesSome steps when doing UATUser acceptance Test planningDesigning UAT Test casesApprove acceptance test planExecuting Test cases Documentation of the defects found during UATResolving the defects fixing.