Category: Agile Testing
-
Building (and losing) credibility as a quality coach
Working as a quality coach or a senior tester is an interesting role, the role may not come with in built authority and so you live and die by the influence you cultivate.
-
Setting up Testing at an Engineering Org
Engineering organizations face unique challenges when setting up testing due to their dynamic and technical nature. In this post I discuss some of the challenges I’ve seen and propose some of the elements needed for your testing strategy in these organisations.
-
Why you really need Automated tests
The market isn’t wrong, you really do need automation, but maybe not for the reasons you’d think. We often talk about needing or types automation and how it helps speed, but not why we really need it. In this post I’ll offer a beginners guide to why automation is needed and helps us.
-
Understanding the things we Need to test
When designing a strategy or approach for testing it’s easiest to start by looking at what it is we have to test. By this I don’t mean the product and features but the common things under test. In this post I discuss what those common things are that we need to test.
-
How to identify the right senior tester for your new Team / Company
NOT ALL TESTERS ARE THE SAME. This can make looking for and hiring a senior in your organisation very tricky. So here’s my helpful tips and tricks for what to look for when hiring a senior (especially if you’re a new team or start up).
-
Why you need testers in a new team
Testing early is important to prevent bugs caused by uncertainty, but we usually don’t think to include testers from the start of a team. This post discusses the needs that teams / organisations early in their life have and the type of testing (and testers) that can help.
-
Testing Doesn’t Just Happen at the End
Testing doesn’t just happen at the end of a project. In this post I discuss testing ideas, designs, and code to save time and build what’s truly needed.
-
How to Involve Developers in Exploratory Testing
Asking developers to start exploratory testing can be hard; many testers haven’t had the opportunity to practise this type of testing, let alone developers. This article will discuss the steps and tips for getting your team (with a focus on developers) involved in exploratory testing.
-
100% Tested is not 100% Covered
100% Tested is not 100% Covered A misconception in testing that we frequently see is the view that if all the tests are run, then the system is fully tested. This leads to the risk of false positives where stakeholders see a 100% tested report and think everything is safe and ready to ship. But
Callum Akehurst-Ryan's Testing Blog 