Agile Testing

Agile Test Reviews and Strategies

Our Agile test strategies aim to build testing within the development cycle so that:

1. Testing is jointly owned by the QA/testers, developers and business/users
2. As much testing as possible is conducted in the iterations/sprints
3. Regression testing is automated and driven from the Continuous Integration server
4. Non-functional requirements and testing are covered
5. New features are accepted by the users during the iterations/sprints
6. Testing covers negative scenarios as well as the "happy path"
7. Any testing not covered in the iterations/sprints is covered before go-live

Using an Agile testing dashboard our Agile test reviews evaluate the testing already implemented and make recommendations for improvements. This process can be rerun a number of times and linked into the retrospective process to drive continuous process improvement.

Agile Test Leadership

Where agile teams do not have the skills to implement agile testing tools and practices themselves we can help by seeding teams with skilled agile testing experts. We can also provide coaching to help bring existing team members up to speed with agile testing tools and techniques.

Agile Expertise

As well as a sound understanding of Agile principles, successful Agile testing requires a high level of expertise in test automation tools which can be used to automate the regression pack and link it into the Continuous Integration (CI) environment. Tools such as FitNesse and Cucumber can be used to automate acceptance testing and support behavioural driven development while tools such as JMeter and Grinder can be used to develop performance tests. All tools need to have a framework in order to integrate them into the Continuous Integration (CI) environment so that the tests are executed every time code is dropped.