Upload
coepd
View
23
Download
0
Embed Size (px)
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/BusinessAnalystTraining Center of Excellence for Professional Development 3rd Floor, Sahithi Arcade, S R Nagar, Hyderabad 500 038, India. Ph# +91 9000155700, [email protected]
Citation preview
(Professional Business Analyst Training
organisation)
Software Testing
Life Cycle ( STLC)
1. Requirement Gathering:
Activities: Prepare the list of question or queries
and get resolved from Business Analyst, System
Architecture, Client, Technical Manager/Lead etc.
Deliverables: List of questions with all answers to
be resolved from business i.e. testable necessities
2. Test Planning:
•Activities: Define object & scope of the project
•List down the testing type drawn in in the STLC.
•Test effort evaluation and resource planning.
•Selection of testing tool if required.
•Define the testing process overview.
•Define the test environment necessary for entire
project.
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.
3. Test case Development
Activities: Preparation of test cases.
Preparation of test automation scripts
Deliverables: Test cases.
Test data.
Test Automation ScriptS
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.
4. Test environment setup:
Activities: Analyze the requirements and prepare the
list of Software & hardware required to set up test
environment. group the test setting.
Deliverable's: Test Environment will be ready with test.
5. Test execution:
Activities: Based on test planning execute the test
cases.
Mark condition of test cases like Passed, Failed,
Blocked, Not Run etc.
Deliverables:Test case execution report.
Defect report.
6. Test cycle closure:
Activities: Evaluate cycle completion criteria based on
Test coverage, value, price, Time, important Business
Objectives, and Software set up test metrics based on
the above parameters.
Prepare Test closure report.
Deliverables: Test Closure report
Test metrics