Flashcards
Untitled
Cards in this deck (4)
- 1Assessing Quality Risks and Estimating Test Effort - A objective to Agile or Traditional projects is to reduce the risk of product quality problems to an acceptable level prior to release
- 2*Assessing Quality Risks in Agile Projects - One of the many challenges in testing is the proper selection, allocation, and prioritization of test conditions -Determining the appropriate amount of effort to allocate in order to cover the tests -The risk identification, analysis and risk mitigation strategies is used by testers to determinate an acceptable number or test cases to executedIn Agile projects, quality risk analysis takes place at two places.
- Release planning: the representative business who know the feature provide a high-level overview of the risk
-Iteration planning: all team identifies and assesses the quality risks - 3Estimating Testing Effort Based on Content and Risk - During the release planning Agile team estimate the effort required to complete the release - Use the planning poker to estimate the effortTechniques in Agile Projects
Acceptance Criteria, Adequate Coverage, and Other Information for Testing
- Non-functional requirements, such as usability and performance, are also important and can be specified as unique user stories or connected to other functional user stories.
- we need to experience from previous project, code, architecture and design, user profiles, existing functions, features, and quality characteristics of the system - 4- The acceptance criteria should address the following topics where relevant *Functional behavior * Quality characteristics - are performance, reliability, usability, etc. * Scenarios use cases *Business rules - activities performed in the system under certain conditions *External interfaces - UI, interface to other systems * Constraints *Data definitions - customer describe the dataThe testers will be need additional information throughout the iterations and we use the concept of the definition of done is critical, as the following sub-subsections
* Test levels - Unite testing, Integration testing, System testing
* User Story - user stories for the iteration are completed, are specified and reviewed, identified and estimated by the team
* Feature - the user stories with acceptance criteria are defined and approved, design completed, code completed, unit test been performed and achieved
* Iteration - all features are ready and tested, integration all features completed and tested, documentation written, review and approved
* Release - include coverage been covered by testing, quality the intensity density and # of remaining defects are within acceptable, time delivery date has been reached and Cost estimate lifecycle cost
Information
- Description
- Flashcards on Untitled, created by daniel sandoval on 28/02/2024.
- Created by
- daniel sandoval
- Views
- 0
- Rating