30 Days of Agile Testing - Day 23: Identifying and organising testing

30 Days of Testing
,
1

The 30 Days of Agile Testing Day 23 task is:

Contribute to The Club how you identify and organise your testing in agile context

How do you identify and organise your testing in an agile context?

1 Like
3

My tests start as soon as possible (shift left):
write or read US with the product, do “Three Amigos” meetings,…
The US has to be testable to be in a sprint.

We start to execute testing when it is possible, in order to give quick feedback ( test can be functional or not, could be done by someone else than QA).

I like to do exploratory testing after huge change.

My main challenge is to prioritized testing with risk and sprint priority.
We can’t test everything :frowning:

1 Like
4

Usually we have a team estimation meeting regarding the feature, Dev and QA give their estimations for the story cards. We then move on to implementation and testing which happens very closely to each other. If a project is really big, then we create a test strategy document and reference the dependencies, links and other useful information within it.

5

Testing starts at the very start of the project, when customer starts talking about the product he/she wants, we(team) starts evaluating the product, the user-stories, the shareholders, etc. Static testing beings right at the start.

With a decent documentation static testing can contribute a lot,

  • Customer understands what he/she really wants from the product
  • Team and the customer stays on the same page

According to product specifications, risk analysis should take place. High impact and high likeliness of a failure should be priorizated. This approach goes for all user-stories(requirements) and a master plan is produced for testing.

6

Starts as early as I can manage. When the stories are being written I should be involved and think ahead on how it should be tested, discuss this and document any thoughts/decisions.
Scripts can be written at this point as well.
Then, as soon as it’s on a non-dev environment testing will start.
When close to release to production some exploratory testing will take place.

1 Like