Testenvansoftware.nl
  • SOFTWARE TESTEN - Blogs
    • Ik zoek werk
  • a test syllabus
  • Wat is software testen?
  • Links
  • C# programming language
  • Testing on Youtube
  • test tooling
  • Test Process
  • Robot FrameWork
  • SOFTWARE TESTEN - Blogs
    • Ik zoek werk
  • a test syllabus
  • Wat is software testen?
  • Links
  • C# programming language
  • Testing on Youtube
  • test tooling
  • Test Process
  • Robot FrameWork

Shooting on a moving target

6/16/2025

0 Comments

 
2019 It's been a while since this blog was created. testenvansoftware.weebly.com/software-testen---blogs/how-to-cope-with-difficulties-in-testing

Sometimes for things of quality it takes time, like a fine wine. I was driving in my car and suddenly it hit me, there's something utterly wrong with this metaphor.

If you see it like this: the horse is the test environment and the goal is to shoot the moving bug... then everybody understands that shooting from something that is moving aiming at something that is moving as well is the hardest scenario. Right?

Bug unclear/moving = 'What exactly triggered the dysfunctioning? was it button1, button2, or.... we need root-cause analysis. It seems to be flaky.'
Environment unstable; example: someone is pushing/merging code while I'm in a test steps procedure of a test case.

Picture
So what is so utterly wrong about the above methaphore?

Well I realized that almost never the tester is a lonesome cowboy like lucky luke. 
Picture
Onwards to 2025: How to Cope with Difficulties in Testing: A Wild West Perspective 

It’s been a while since this blog first galloped onto the scene--testenvansoftware.weebly.com—and like a fine wine (or a stubborn bug that only surfaces at 4:45 PM on a Friday), again, some things take time to mature. But recently, while driving, it hit me: the wine metaphor doesn’t quite fit testing. Let’s holster that analogy and ride into something more fitting: the cowboy way.
The Wild West of Testing: Shooting Bugs from a Galloping HorsePicture this:
  • The Horse = Your test environment (unpredictable, occasionally spooked by a rogue database or a misbehaving server).
  • The Cowboys = Testers, balancing precariously while trying to take aim.
  • The Eagle = That elusive, flapping-in-the-wind bug you’re trying to shoot.
Now, imagine trying to hit a moving target while riding something that’s also moving. That, my friends, is the essence of testing. The environment shifts, the code evolves, and yet--yeehaw!—you’re expected to land the perfect shot.
Communication: The Saloon Talk of TestingA tester doesn’t ride alone. There’s a whole posse involved: developers, PMs, other testers. And just like in a spaghetti Western, miscommunication can lead to unintended showdowns.
Example:
  • Dev says: “The concert is in the park tomorrow.”
  • Tester hears: “Tomorrow, concert… or park? Wait, is the park closed? Is the concert canceled? Did we just pivot to a rodeo?”
Distilling clarity from chaos is a tester’s superpower. But it’s not just about parsing words—it’s about recognizing that every link in the chain (code, env, data, human whispers) introduces its own turbulence.
The Takeaway: Embrace the RideTesting is less like sipping wine and more like staying atop that galloping horse:
  1. Expect the horse to buck (envs will break).
  2. Aim ahead of the eagle (anticipate edge cases).
  3. Yell loud at your posse (communicate relentlessly).
So saddle up, partner. The frontier of quality is vast, unpredictable, and occasionally ridiculous. But that’s what makes it fun.
Now, who’s got the drinks? We’ve got bugs to hunt.
Picture
0 Comments

Designation of Priority and Severity

2/6/2025

0 Comments

 
Picture
Picture

Rule #16 of the Break Software Testing Methodology states: There may be absolutely NO ambiguity of any kind in the designation of Priority and Severity of items.

But what does this really mean? Let's take a closer look.
As software testers, we’re all familiar with Jira, right? We often encounter terms like Highest, High, Medium, Low, and Lowest. But here’s the problem: these terms are sometimes used for both Priority and Severity, which can be confusing.
​
When a bug is found, you’re typically required to fill in the fields for Priority and Severity before you can save the page. But who decides whether the severity is High, Medium, or Low? And who determines the priority level?
Usually, it’s based on the current insights of the person logging the bug. In other words, it’s often a personal judgment. Many times, people simply leave the default value, which tends to be Medium. That’s not very productive or wise, is it?
Now, let’s bring Agile Scrum into the conversation. What determines what we work on first? The things that provide the most value to the Product Owner, right? So, does filling in the Priority and Severity fields actually have any meaningful effect?

Without clear rules in your test policy about the chronological order of working on items, things can quickly get messy and chaotic.

Picture
Tip! Make sure that the same terms are not used for both Severity and Priority. For example, instead of using High, Medium, and Low for both, you could use High, Medium, and Low for Priority, while using terms like Critical, Major, and Minor for Severity.

Additionally, clarify who sets these values. Is it a person? A team? At what point are these values considered final?
And most importantly—actually use this in your process! Describe how it works and ensure the team follows it.
Afterall there is no "state when found set by Marc" vs "state after stand-up set by Team" or something similar. There's just a state of Priority and state of Severity. Right?


Otherwise, you might find yourself unable to continue testing because certain items were initially taken for granted but later turned out to block the entire process.
Picture
Here’s a simple scenario to test your decision-making:
There’s one day left in the Sprint, but a major bug remains unfixed and untested, requiring two full days of work. On top of that, a software tester reports a new bug with the highest severity but assigns it the lowest priority — a decision some team members find highly questionable.
How does your Scrum team handle this situation? Is this approach aligned with your testing process? Does your test policy provide any guidance on this?
The reality, however, is often far more complex than this simple scenario:
The newly raised bug has dependencies on the existing bug. Is fixing these bugs less important than completing the new functionality? If they all have the same priority and severity, it becomes even harder to determine the best course of action. But if we finish the new functionality first and fix the bugs afterward, who will test whether the new functionality still works after the bug fixes?
Do you see how complex it can get? Software testing can be mind-boggling at times.

Realistic testers know, in practice it's sometimes even waiting till the moment someone says:
Ohw I see something... there is a comment in the ticket... I guess the requirements just changed and we need to re-test... ...again. ;)
0 Comments

Software tester, complot-theorist or realist!?

1/23/2025

0 Comments

 
Remember that previous blog? Specialist or Jack-of-all-trades?
Given the current zeitgeist, I thought it was time for a fresh perspective.
As a software tester, are you someone who believes in conspiracy theories, or are you more of a realist?

Let’s weigh some pros and cons...

If you say: "Someone who believes in conspiracy theories," that aligns with traits like looking beyond the obvious and thinking outside the box. How often are you searching for the root cause, the true source of a problem? In those moments, you need to think creatively — with cork, string, or whatever else comes to mind.
If you say: "A tester must be an absolute realist," there’s merit to that too. After all, you’re often dealing with schedules, deadlines, and limited time. What’s the point of diving into areas that might not even be relevant? There are solid arguments for this approach as well.

Personally, I think the conspiracy thinker — as long as they don’t go overboard — tends to have the upper hand. This mindset is more aligned with finding alternative paths and trying different approaches that might lead to discovering bugs. If you never think deeper — even if some ideas seem a bit “far-fetched” or “strange” — then perhaps this might not be the right profession for you.
​
But what’s your opinion? I’m curious to hear your thoughts!
Picture

    My opinion....

Submit
0 Comments
<<Previous
    Picture
    Amazon books on software testing
    Picture

    Categories :

    All
    English Blogs
    Nederlandse Blogs


    Picture
    Check it out! A new software test methodology
    Picture
    The Forum for the Methodology
    Picture
    Lees meer blogs over software testen
    Blogs over software testing
    120 unieke bezoekers per week.
    Uw banner ook hier?
    Dat kan voor weinig.
    Tweet naar   @testensoftware
    Follow @testensoftware
    Tweets by testensoftware

    Author

    Motto:
    'Quality is a choice!'


    Foto
    De beste boeken over software testen...
    Foto
    Wat een tester nodig heeft...
    Artikelen over software testen... in het Nederlands: infonu.nl

    Archives

    June 2025
    February 2025
    January 2025
    December 2024
    March 2024
    February 2024
    November 2023
    October 2023
    September 2023
    July 2023
    June 2023
    May 2023
    March 2023
    January 2023
    November 2022
    September 2022
    August 2022
    July 2022
    May 2022
    January 2022
    November 2021
    October 2021
    May 2021
    April 2021
    August 2020
    July 2020
    June 2020
    April 2020
    March 2020
    February 2020
    January 2020
    May 2019
    February 2019
    January 2019
    December 2018
    November 2018
    October 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    July 2017
    May 2017
    April 2017
    March 2017
    December 2016
    November 2016
    August 2016
    February 2016
    December 2015
    September 2015
    August 2015
    March 2015
    February 2015
    January 2015
    November 2014
    October 2014
    September 2014
    August 2014
    July 2014

    This website uses marketing and tracking technologies. Opting out of this will opt you out of all cookies, except for those needed to run the website. Note that some products may not work as well without tracking cookies.

    Opt Out of Cookies
Powered by Create your own unique website with customizable templates.