Do you remember a time when you prevented an issue? - STEC 1.2.0

Discussions
, ,
1

I remember a time when I didn’t prevent one. And as Ady Stokes said in the second lesson of STEC’s first module: “This is not just about stories of failure—we should seek stories of success too.”

When it comes to explaining the value of testing, failure stories can be powerful for showcasing its necessity. But preventing failures is far from the only value software testing brings!

Testers today do more than just ensure there are no bugs in the product. The value of testing isn’t in the number of bugs found.

:light_bulb: It lies in understanding what the software does, clarifying requirements for everyone, and ensuring nothing is overlooked during the ideation phase.

:national_park: It lies in understanding the big picture. Testers can contribute at nearly every step of the development process. As Ady describes: “For software testers, our work shows up in things like finding problems, identifying risks, setting up processes, figuring out what to observe, making sense of data, considering end users’ needs, the feedback we get, and, of course, finding bugs.”

:fire: It lies in understanding business risks—so the business can make informed decisions.

And so on.

All of this actually contributes to preventing issues! And today, I feel like getting some positive energy. So I’m taking Ady’s advice and asking: What are your success stories? :grin:

4 Likes
2

So currently we are using same codebase for most of the projects in my organization and there is very high chance that there is any issue in any project due to impact of code change then that issue may be in other projects also.

So once we notice issue in one project we promptly inform the developers and EMs about the issue due to code change and they fix the code before merging it for other projects.

This is one of the way we try to prevent issue.
There is also likely chance that the isue occur in one project may not occur also in other project but still to save time and effort we keep everyone in loop about the bug we noticed.This way, developers also know the potential impact of code on other projects, PMs and EMs are also aware about the impact

This is one of the way we try to prevent issues.

4 Likes
3

Totally agree! :glowing_star:
The earlier an issue in the SDLC is found, the lesser cost it is for business. I think that is the ultimate role of a Tester. Getting involved as early as possible have its perks!

3 Likes