4.5 Collaboration-based test-approaches Flashcards
What are the key components of a user story?
A user story consists of the “3 C’s”: Card (medium for description), Conversation (explanation of how software will be used), and Confirmation (acceptance criteria).
What does the acronym INVEST represent in user story development?
INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable. These criteria help in defining good user stories.
How do acceptance criteria contribute to user story development?
Acceptance criteria define the conditions that an implementation must meet to be accepted by stakeholders. They serve as test conditions and guide acceptance testing.
What is the benefit of collaborating on user story creation?
Collaborative authorship, using techniques like brainstorming and mind mapping, helps teams achieve a shared vision of project deliverables while considering perspectives from business, development, and testing.
What role do acceptance criteria serve in user story acceptance?
Acceptance criteria define the scope, facilitate stakeholder consensus, describe scenarios, guide acceptance testing, allow accurate planning and estimation, and provide a basis for user story acceptance.
What are the primary formats used for documenting acceptance criteria?
The two most common formats are scenario-oriented (e.g., Given/When/Then format from BDD) and rule-oriented (e.g., bullet points or tabulated form).
What is the approach of Acceptance Test-driven Development (ATDD)?
ATDD is a test-first approach where test cases are created prior to implementing a user story. It involves team members from different perspectives (customers, developers, testers) collaborating to define and create these tests.
How are test cases typically generated in Acceptance Test-driven Development (ATDD)?
Test cases are derived from the acceptance criteria of the user story, ensuring that they cover both positive and negative scenarios. They serve as examples of how the software should behave.
Why is it advantageous to document acceptance tests in a format compatible with test automation frameworks?
When acceptance tests are written in a format supported by automation frameworks, developers can automate these tests alongside implementing the user story. This ensures that acceptance tests become executable requirements and can be easily integrated into the development process.
