4.5 Collaboration-based Test Approaches Flashcards
All test techniques focus on defect detection. What makes Collaboration based approaches different?
They also focus on defect avoidance through communication and knowledge sharing.
What is the most common format for a User Story?
As a [role], I want [goal to be accomplished], so that I can [resulting business value for the role]. Following this is the acceptance criteria.
What are the three critical aspects of User Stories?
Card - the medium describing the user story
Conversation - how the software will be used
Confirmation - acceptance criteria
What does a user story represent?
A feature that will be valuable to either the user or the purchaser of a system or software.
What benefit does collaborative user story writing offer?
The team can obtain a shared vision of what should be delivered by taking into account three perspectives: business, development, and testing.
What is the acronym used to describe a good user story?
INVEST: Independent, Negotiable, Valuable, Estimable, Small, and Testable
What are Acceptance Criteria?
Conditions that an implementation of the user story must meet to be accepted by stakeholders. They are effectively the test conditions that should be exercised by tests.
How are Acceptance Criteria used?
- define the scope of the story
- reach consensus among stakeholders
- describe positive and negative scenarios
- serve as a basis for acceptance testing
- allow accurate planning and estimation
What are the most common formats for writing acceptance criteria for user stories?
- Scenario-oriented: Given/When/Then as in BDD
- Rule-oriented: bullet point verification list, tabulated form of input/output matching
Other formats are possible and fine so long as they are well-defined and unambiguous.
What is ATDD?
Acceptance Test Driven Development is a test-first approach. Test cases are created prior to implementing user stories. These cases are created by team members with various perspectives, including users, developers, and testers.
What are the steps of ATDD?
- Specification workshop where user stories and acceptance criteria are analyzed, discussed, and written by team members. Incompleteness, ambiguity, and defects in the story must be resolved at this time.
- Write Test Cases. Cases are based on acceptance criteria and can be seen as examples of how the software works.
Are the first cases written and tested usually positive or negative? What’s the difference?
Generally positive first, then negative, and then other non-functional quality characteristics are tested.
Positive test cases confirm expected functionality without exceptions or error conditions (essentially the golden path).
Negative cases test using error conditions, exceptions, and other situations that might be considered ‘unexpected’ or not along the golden path.
Should multiple test cases cover the same characteristics of a user story?
No, no two test cases should describe the same characteristics of the user story.
What coverage should test cases for a user story provide?
The test cases must cover all the characteristics of the user story and should not go beyond the story. However, the acceptance criteria may detail some of the issues described in the user story. In addition, no two test cases should describe the same characteristics of the user story.
What is the benefit of capturing test cases in a format supported by a test automation framework?
The developers can automate the test cases by writing the supporting code as they implement the feature described by a user story. The acceptance tests then become executable requirements.
