Agile Testing

To work with agile testing means being prepared to adapt to changes in a continuous manner. People who prefer to work in a traditional environment will usually find it difficult to adapt to this kind of process.

The strategy applied in an agile testing environment must be different from the one applied with traditional testing. The current world is running faster than ten years ago, and the market expects testers to work more and more under pressure, while still reaching better and faster results.
In this sense, it is more important to prioritise interactions between co-workers than following process and tools; Guaranteeing that the software works is more important than having a comprehensive documentation; And finally, showing the results from changes is more important the following a pre-defined plan.

My experience:

When I started working on an agile environment, I had no idea what it was to work in such environment. Also, the team had a history of QA analysts jumping out of the project before
The team lead and the customer PM usually switched from giving tasks while following the manual process, but only when project was “on time” to do it.
The tipping point happened when the customer decided update some screens, and asked the QA team to just ignore the test cases and begin testing with little to no documentation. This is when I understood why the past QA professionals were demotivated and usually did not last long in the project. Then I decided to give it a shot and just adapt myself to this new environment.

I started to study about process, and I discovery about Testing in an agile environment. It is incredible how similar what it tries to fix and the situation I had at the moment.
So I began to study, search. What could I do to improve the methodologies we used internally? And then I learned it is important to have a good knowledge about the system you are testing. It is essential to discuss every doubt with your team, and most importantly with the business analyst.

In the end it helped me bring really nice results, as I was able to understand how the project was done for the end users, and how to properly test whatever is important for these users. It also showed me how to work with exploratory testing, as I did not have a plan I could follow, and every day I just had to sit in my chair and think where and how this new change could affect the product I was working on.

Basically speaking, QAs need to be more proactive to work in an agile environment, while still prioritising relationship with the client as well as the developers.

Leave a Reply

Your email address will not be published. Required fields are marked *