Flashcards
3.3 Techniques in Agile Projects
Cards in this deck (10)
- 13.3.1 Acceptance Criteria, Adequate Coverage, and Other Information for Testing
- 2Agile Project Requirements:⏺User stories prioritize project requirements.
⏺Non-functional requirements (e.g., usability, performance) may be unique stories or linked to functional ones. - 3Test Basis:Besides user stories, test bases include past project experiences, system features, code, and user profiles.
- 4Acceptance Criteria:Essential for acceptance testing, covering functional behavior, quality characteristics, scenarios, and more.
- 5Additional Information for Testers:💥Includes system usage, interfaces, tool support, and tester skills.
💥Collaboration with the team helps gather needed details. - 6Definition of Done for Test Levels:✅Unit Testing: Complete code review, no unresolved major defects, all tests automated.
✅Integration Testing: All requirements tested, interfaces checked, no major defects unresolved.
✅System Testing: End-to-end tests, key quality characteristics covered, all defects reported and possibly fixed. - 7Definition of Done for User Stories, Features, Iterations, and Releases:🟢User Story: Complete, understood, tested with acceptance criteria.
🟢Feature: Approved user stories, complete design and code, tested with defined coverage.
🟢Iteration: Features tested and integrated, documentation completed.
🟢Release: Adequate test coverage, acceptable defect intensity and density, business considerations met. - 83.3.2 Applying Acceptance Test-Driven DevelopmentAcceptance Test-Driven Development (ATDD) is a test-first approach where test cases are created before implementing user stories.
- 9Process:1️⃣Specification Workshop: Developers, testers, and business representatives analyze and discuss the user story, fixing any issues.
2️⃣Test Creation: Tests are created, either collaboratively or individually, ensuring they describe specific user story characteristics.
3️⃣Validation: Tests are validated by an independent person, such as a business representative, to ensure accuracy.
4️⃣Test Types: Positive tests confirm correct behavior, followed by negative path tests and coverage of non-functional attributes (e.g., performance).
5️⃣Language and Clarity: Tests are expressed in natural language, ensuring clarity for all stakeholders. - 10Guidelines:✳✳Tests should cover all user story characteristics without adding new ones.
✳✳Each example should be unique, covering different aspects of the user story.
ATDD promotes collaboration among team members and ensures that user stories are well-understood and accurately implemented.
Information
- Description
- 3.3.1 Acceptance Criteria, Adequate Coverage, and Other Information for Testing 3.3.2 Applying Acceptance Test-Driven Development
- Created by
- Esther H
- Views
- 16
- Rating