Agility & Testing-part 2

This is in continuation with the previous blog on the same topic

Agile testing

Testing practice that follows the agile manifesto, treating development as the customer of testing

Successful Agile has -

* Team
* Strategy
* Continuous Integration
* Test automation


What’s so different about Agile testing?

Role of testing
* Testing is the headlights of the project
* Testing provides information to the team – allows the team to make informed decisions
* A bug is anything that could bug a user – testers don’t make the final call.
* Testing does not assure quality – the team does(or doesn’t)
* Testing is not a game of “Gotcha” – find ways to set goals, rather than focus on mistakes

Now follows the testing methods which are following in Agile testing -

Test Driven Development Vs Defect Driven testing
TDD
* Write a Test That Fails
* Write Just Enough Code
* Repeat
* Creates a Solid Product

DDT
* Find a Bug
* Add a Test
* Jazz It Up
* Incrementally Builds Suite
* Retrofit

Test-First Programming
* Developers write unit tests before coding
* Motivates coding
* Improves design(reducing coupling and improving cohesion)
* Supports refactoring
* Many open source test tools have been developed to support this like Junit, Xunit.

Acceptance Testing
* Goal is to accept the User Story in the Iteration – passing acceptance tests
* Ideally they are written before coding.
* Purpose is to reflect “doneness” at the customer level – accepted

Exploratory Testing
Testing while learning, Learning while testing.

What happens in agile testing?

* Detect abnormalities the moment they happen.
* Don’t fight fires!
* Find and fix the problem.
* Determine the root cause - Why? Why? Why? Why?
* Investigate Countermeasures - Try several and see what works
* Implements the best solution

An Iteration

Automation in Agile Testing
Used for regression mainly, as there is always a new build ready and less time for testing. but there are challenges.

Challenges/risks of using tools