3.3.1 Acceptance Criteria, Adequate Coverage, and Other Information for Testing Flashcards
(23 cards)
What outlines initial requirements in Agile projects?
User stories in a prioritized backlog
What are non-functional requirements in Agile projects?
Requirements such as usability and performance
What can serve as a test basis in Agile projects?
Experience from previous projects, existing functions, code, architecture, user profiles, defect information, standards, quality risks
What is the purpose of acceptance criteria in Agile?
To ensure testability by addressing functional behavior, quality characteristics, scenarios, business rules, external interfaces, constraints, and data definitions
What does functional behavior refer to in acceptance criteria?
The externally observable behavior with user actions as input
What are common quality characteristics?
Performance, reliability, usability
What are scenarios in the context of acceptance criteria?
A sequence of actions between an external actor and the system to accomplish a specific goal
What are business rules in Agile projects?
Activities that can only be performed under certain conditions defined by outside procedures
What are external interfaces?
Descriptions of connections between the system and the outside world
What should be included in the definition of done for unit testing?
100% decision coverage, static analysis, no unresolved major defects, all code reviewed, all unit tests automated, important characteristics within agreed limits
What does integration testing ensure?
All functional requirements tested, all interfaces between units tested, all quality risks covered
What is included in system testing?
End-to-end tests of user stories, coverage of user personas, testing in production-like environments
What defines the completion of user stories?
User stories are complete, understood, and have detailed acceptance criteria
What must be true for the definition of done for features?
All user stories defined, complete design, complete code, unit tests performed, integration tests performed, no major defects
What does the definition of done for an iteration include?
All features ready and tested, non-critical defects prioritized, integration of features completed
What areas are covered in the definition of done for a release?
Coverage, quality, time, cost
What does coverage refer to in a release?
All relevant test basis elements covered by testing
What is the significance of defect intensity?
It measures how many defects are found per day or per transaction
What does the estimated lifecycle cost help determine?
The return on investment for the delivered system
True or False: All iterations in Agile projects result in a release.
False
What should testers work collaboratively with Agile team members to obtain?
Additional information needed throughout iterations
What is critical in Agile projects regarding the definition of done?
It applies in multiple ways across different project aspects
What may be added to the product backlog if not fixed within an iteration?
Non-critical defects
