The 9 Principles of Agile Testing

Agile testing is a software testing practice that follows the principles of agile software development.
You can use that 9 principles like a checklist if  the question you would like to ask yourself: "How Is Agile Testing work?"

1. Shifting focus

From being the last in line of defense in traditional projects with Agile QA provides information, feedback and visibility on an ongoing basis about how well the emerging product meets the business needs. The adverse relationship between testers and developers must be replaced with a Spirit of collaboration.

2 .Testing is not just a phase

Development and test should be integrated. Continues testing is the only way to ensure continuous progress.

3. Tested is part of DONE

Out of Agile, it is typical to say that a feature is DONE after the implementation is done by the developers. According to Agile a feature is DONE when it is implemented and tested.

4. Everybody tests, not just the designated testers

If the developers are going fast, but testing is not done, than implementation is not done, so the features are not done- team gets wrong feeling for the velocity it has.

5. Reduce feedback latency

The time between the developer writes a line of code and when someone /something executes that code and provides information about how it behaves, is a feedback loop. Long gaps between implementing and testing increase risk and waste. That is why Agile Teams test early and often.

6. Tests represent expectation

It is a challenge to find the balance between testing for implicit expectations and making requirements up on the run. Sometimes the expectations turn out to be unreasonable, so before huge amount of time is spent testing for a given risk, questions should be asked to clarify the expectations with the project stakeholders.

7. Bugs do not hang around

An Agile Team should have discipline to fix bugs as they are found. If it is a genuine bug, as opposed to a new story, it is fixed within an iteration. Main principle is fix bugs quickly and keep the code clean.

8. Reduce test documentation overhead

Agile testers use reusable checklists to suggest tests, focus on the essence of the test rather than the incidental details, use lightweight documentation styles and tools, capturing test ideas in charters for Exploratory testing, leverage documents for multiple purposes.

9. From test last to test driven

Defining the tests with the requirements, rather than after, and using those tests to drive the development effort, gives much more clearly done criteria and shared focus on the goal.

Enjoy :-)