Category: Agile Testing
-
Why aren’t we Talking about Shift Right in Quality Engineering?
With there being more buzz and discussions around Quality Engineering, I’m seeing more people discussing shift left as part of what testers do. But what about shift right? In this post I’ll explore the basic ideas of shift right and provide my thoughts on why we don’t talk about it so much (because it’s hard).
-
Want to be a better Quality Engineer: Lose the Ego
A great Quality Engineer needs to put humility over their ego. We don’t need to win, instead we need collaboration and influence within teams to improve quality.
-
Quality Coaching Scenario: This code won’t take tests
In this post I’ll take a hypothetical testing scenario and then set out the thinking I’d take around it to support the organisation as a quality coach. The aim here is to help people to see the thinking that I’d undertake as a way of helping to shape other people’s thinking and provide some materials…
-
Testers have to be the ones to advocate for quality
There’s a prevailing commentary that quality professionals not only are the only ones thinking about quality but also need to fight for a seat at the table to discuss these things. Testers need to be the ones advocating for quality because we’re the ONLY ONES WHO CAN.
-
Quality Coaching Scenario: No testing happening
In this post I’ll take a hypothetical testing scenario and then set out the thinking I’d take around it to support the organisation as a quality coach. The aim here is to help people to see the thinking that I’d undertake as a way of helping to shape other people’s thinking and provide some materials…
-
You don’t need so many E2E tests (or do you?)
We’ve all seen the testing pyramid, a diagram that shows us that proportionally we should reduce the amount our larger tests in favour of smaller ones. Yet we see so many teams still relying primarily on larger end to end tests, why is that? More importantly, is that a problem?
-
Your product is more than just features
We often reduce our product to the things they do, assuming that it’s the features that make people want to buy and use it. But this only forms part of the story, it’s not only WHAT a product does but HOW it does it that can make it saleable and profitable in the long term.
-
A lack of standard (testing) terms hurts us all
A lack of standardized terminology in the testing industry complicates communication among testers, hiring managers, and other engineers. This discrepancy can lead to misunderstandings, inefficiencies in onboarding, and reduced credibility. In this post I talk about how a lack of standard terms can hurt us and how we can mitigate that pain.
-
Getting into quality engineering: Bookend development
Moving into quality engineering means being more involved with development and engineering practices; something that can be very overwhelming and daunting to get started with. So where do we start as testers moving into this space? By bookending development (coding) and being a part of the start and finish of things.
-
Is it really an edge case?
It’s a tale as old as time, as testers we raise a risk or a bug only to be told “that’s an edge case so it won’t be taken into account”. But is that really true, what’s an edge case and should we care?
Callum Akehurst-Ryan's Testing Blog 