Explore Selenium

Selenium Automation



Normally in Agile Teams testers become team members, but what exactly Tester’s role in agile testing is explained in this post.

This raises an ominous question for testers and QA professionals: “If everyone on the team is responsible for testing, is the tester’s role still needed?”

The answer is a resounding YES.

 Role of Testers in AGILE:

Testers and developers possess different skill sets.

They approach problems differently. Their training and experience shape their perspectives on a project or a product. They look at the same user story and see different things.

Traditional development practices segmented people by skills and roles.

So, what’s the value add of having a skilled Tester on your team?

Testers are the voice of the customer.

They know how to separate the design and intended use of the application under test from the way the end-user will actually use and interpret the system. Testers help product owners clarify acceptance criteria and understand risks. They help the team define “Done”.

Testers add focus.

Testers work with developers to ensure that what is being built is the product that is needed. Agile testing provides ongoing feedback about how well the product-in-progress is meeting the business needs and product requirements.

 Testers are always testing.

Teams with testers test early and often, and continuous testing equals continuous quality. Embedding testers on teams helps the teams in the points when the developer writes the code, the code is executed, and information is provided about how the code behaves by testing it.

 Testers help teams find bugs early and fix them fast.

Instead of waiting until the code is developed to figure out if the acceptance criteria is met, and scrambling to fix the bugs before the product has to ship, development and testing occur concurrently on Agile teams.

 Testers ensure that regression testing is a continuous process.

When regression testing is built into the development process, as soon as code is loaded into the build, it can be tested. Quickly identifying the code that doesn’t work means that the team doesn’t have to undo the days of work to get to the source of the bug. This is key to reducing duplication and wasted effort.


Agile teams do not view testing as a step in the process of software development. Instead, agile testing, which requires testers, is a way of working that gives teams confidence that the work they have completed to date meets the customer’s expectations.

Testers don’t develop software but make it better

Agile Process and Terminology
Mind Mapping Techniques in Software Testing

1 Comment

  1. Smithe620

    I was suggested this blog by my cousin. You are wonderful! Thanks!

Leave a Reply