Member-only story
Concepts and components of testing strategy in an Agile environment
Nowadays, the majority of team are working in an agile environment, where we work in short sprints, and an iterations of 2 to 4 months, each sprint is focused on only a few user stories. One of the drawback — and fortunately — is to have less extensive documentation and less extensive test plan. Still we do require a high-level agile testing strategy as a guideline for the agile teams. Its purpose is to draw a structure that the teams can follow.
Related articles :
- Testing Terminology, testing vocabularies and definitions reference
Testing Strategy
A testing strategy usually has a mission statement which could be focused on the software being built or may be related to the wider business goals and objectives. A typical mission statement could be:
To constantly deliver Working Software that meets customer’s requirements by preaching the concept of ‘providing fast feedbacks’ and ‘favouring defect prevention’ rather than ‘defect detection’.
That statement reflects a few but not exhaustive values and principles of the agile manifesto.
And to support that statement, we may apply to some best practices and we may use these four rules:
