Software testing

Practical software testing articles from DoesQA: resilience, flakiness, coverage, and shipping with confidence.

Stop Guessing, Start Testing with Data

APM is not just for ops teams watching production dashboards. For testers, it is a practical source of truth. This article breaks down five ways APM data helps testers stop guessing, focus regression where it matters, strengthen exploratory testing, write clearer bug reports, and feel more confident in their decisions. If you want your testing to be guided by real usage instead of assumptions, this is a solid place to start.

Stop Guessing, Start Testing with Data

APM is not just for ops teams watching production dashboards. For testers, it is a practical source of truth. This article breaks down five ways APM data helps testers stop guessing, focus regression where it matters, strengthen exploratory testing, write clearer bug reports, and feel more confident in their decisions. If you want your testing to be guided by real usage instead of assumptions, this is a solid place to start.

Stop Guessing, Start Testing with Data

APM is not just for ops teams watching production dashboards. For testers, it is a practical source of truth. This article breaks down five ways APM data helps testers stop guessing, focus regression where it matters, strengthen exploratory testing, write clearer bug reports, and feel more confident in their decisions. If you want your testing to be guided by real usage instead of assumptions, this is a solid place to start.

APM is not just for ops teams watching production dashboards. For testers, it is a practical source of truth. This article breaks down five ways APM data helps testers stop guessing, focus regression where it matters, strengthen exploratory testing, write clearer bug reports, and feel more confident in their decisions. If you want your testing to be guided by real usage instead of assumptions, this is a solid place to start.

The first rule of Test Automation

A test case should be repeatable. There is an age-old example of how this can be done badly.

The first rule of Test Automation

A test case should be repeatable. There is an age-old example of how this can be done badly.

The first rule of Test Automation

A test case should be repeatable. There is an age-old example of how this can be done badly.

A test case should be repeatable. There is an age-old example of how this can be done badly.

All new code is sh*t!

Sounds controversial? It's not! We can all think of examples of shit code, maybe from code we committed or famous stories from Google, Nasa, Moonpig, etc, etc... etc.

All new code is sh*t!

Sounds controversial? It's not! We can all think of examples of shit code, maybe from code we committed or famous stories from Google, Nasa, Moonpig, etc, etc... etc.

All new code is sh*t!

Sounds controversial? It's not! We can all think of examples of shit code, maybe from code we committed or famous stories from Google, Nasa, Moonpig, etc, etc... etc.

Sounds controversial? It's not! We can all think of examples of shit code, maybe from code we committed or famous stories from Google, Nasa, Moonpig, etc, etc... etc.

🎥 Testing Navigation

This video looks at some basic navigation Nodes in DoesQA, including Go To, Back, Forward and Reload.

🎥 Testing Navigation

This video looks at some basic navigation Nodes in DoesQA, including Go To, Back, Forward and Reload.

🎥 Testing Navigation

This video looks at some basic navigation Nodes in DoesQA, including Go To, Back, Forward and Reload.

This video looks at some basic navigation Nodes in DoesQA, including Go To, Back, Forward and Reload.

What level of coverage is considered good?

A good level of coverage in software testing typically ranges between 70% to 80%. It varies based on the project's complexity, risk, and specific requirements.

What level of coverage is considered good?

A good level of coverage in software testing typically ranges between 70% to 80%. It varies based on the project's complexity, risk, and specific requirements.

What level of coverage is considered good?

A good level of coverage in software testing typically ranges between 70% to 80%. It varies based on the project's complexity, risk, and specific requirements.

A good level of coverage in software testing typically ranges between 70% to 80%. It varies based on the project's complexity, risk, and specific requirements.

Is Automation Replacing Manual Testing?

No, manual testing is not being replaced. It continues to play a vital role in software quality assurance by providing unique insights into user behaviour and ensuring exceptional user experiences.

Is Automation Replacing Manual Testing?

No, manual testing is not being replaced. It continues to play a vital role in software quality assurance by providing unique insights into user behaviour and ensuring exceptional user experiences.

Is Automation Replacing Manual Testing?

No, manual testing is not being replaced. It continues to play a vital role in software quality assurance by providing unique insights into user behaviour and ensuring exceptional user experiences.

No, manual testing is not being replaced. It continues to play a vital role in software quality assurance by providing unique insights into user behaviour and ensuring exceptional user experiences.

DoesQA Flows dashboard

Get your next release tested end to end.

Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.

DoesQA Flows dashboard

Get your next release tested end to end.

Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.

Get your next release tested end to end.

Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.