You need to know what's on the cutting-edge of technology. Find out what's coming and the unique Warptest POV with just one click on the "Blog" tile.

All posts tagged bug reporting

The Art of Software Testing Relies On…

Several critical truths. One of these is, “A bug not reported will never get fixed.”

The corollary of this according to Schroedinger-Murphy is, “This bug will return to bite you in the * at the worst possible time.”

Never Has There Been A Tale Of More Woe…

(Poetic license and changes of name and gender have been used to protect the innocent in this story)

Once upon a time, Bob the tester was working on a testing project with a new feature. Bob was testing this feature which relied on a 3rd party backend service and another 3rd party client plugin.

Bob had tested a prior version and declared the feature as working but in the latest version he found bugs with UI and function.

His manager, Jim got involved after he heard Bob explain to the Developer the problems and the Dev and their manager said, “This is an issue with the 3rd party integrations. We can’t do anything.”

Software Testing - We can't fix this

Jim asked Bob one question, “Are the issues documented in our Bug Tracking?”

Bob shook his head and could see Jim was not pleased.

Software Testing - Jim Khaaaan

Image screen captured from Youtube clip from Star Trek 3: The Wrath of Khan

“Bob. I must have said this a hundred times. Dev doesn’t decide if a bug gets reported, bug reporting means all bugs with the appropriate severity, Bob.”

Bob went back to his computer and was about to document the bugs when he said, “Hey Jim should these bugs all be reported as one bug?”

Jim came over and sat down with Bob, drained his coffee and said, “If they are all facets or symptoms of the same bug then maybe but ask yourself this Bob. If a Developer marks the bug fixed and you have multiple issues in there, how do you know which are fixed? More to the point, if some of these issues aren’t fixed what status does the bug acquire?”

Bob thought about it for a few seconds, grinned and told Jim he was going to open a bug for each. Jim slapped him on the back and went back to his desk.

The Warptest POV

Software Testing and Bug Reporting is somewhere between an art and a science. It is rule based and if you don’t want to cock-up, these fundamental rules need following.

What happens after you document bugs you discover and allocate the right priority is the next step in delivering a robust, sellable product that makes happy customers.

The basics of Software Testing can be learnt and then the skills and experience acquired through hands-on practice. Luckily, the nature of Software Testing is repetitive like Kata.

So as you sit down with your coffee to test the latest deliverable, make sure you are sharing information with good bug reporting.

Happy Testing.

Bug Reporting Is As Much An Art As A Science

… As a result sometimes running a refresher / brainstorming session on best practices in bug reporting for your team is a must.

As I’ve mentioned in the past, the testers and the person presenting can benefit hugely from the interaction.

The Primer

Embedded here is a primer presentation I use for this refresher on aspects of bug reporting I want my team to focus on:

The Warptest POV

Whether you are working with onsite developers or offshore, the need for sound observation and good bug reporting is critical.

A bug not reported or not reported properly will never get fixed. If your bug reports don’t give objective analysis or stress the severity / cost to the end-users then the bug may never get fixed.

So maximize your testing ROI and make sure every bug discovered and reported gets a fair chance a being fixed.

Do you refresh your bug reporting skills at least once a year?

Google Project Zero Is a Project…

…where Google discovers security bugs (not exclusive to their own software or technology) and once they notify the owner of said software the countdown clock begins.

Once 90 days ends Google will as threatened reveal the bug publically.

google project zero - site

Screencapture: from the Google Project Zero homepage

The idea behind this is to encourage a safer internet for all but there are inherent questions when it comes to Google and Microsoft.

Vendetta

The long running feud between Google and Microsoft has displayed a variety of outright hostile behaviors: –

  • Microsoft’s Scroogled campaign.
  • Google’s repeated blocking of apps like Google Maps or YouTube from making it onto Windows Phone (after working in collaboration with Microsoft to develop the app).
  • Google’s attempts to shut down ActiveSync in favor of their own CalDav and CardDAV.
  • Microsoft’s GMailman Ad.

These and many more reflect the harsh competition between the two companies in many areas:

Search, Location, Online Productivity Apps, Cloud Storage, Mobile, Mobile Apps, Operating Systems, Browsers and more.

Forget about “Hello I’m a Mac and I’m a PC”. This isn’t just negative marketing but has reached a point where users are being affected.

Get a Mac Ad courtesy of YouTuber LukePuuk

The Warptest POV

The main concern is that this situation seems to be only escalating and the consumer may benefit long term but could be harmed in the short term… DO NO HARM .. remember that?

The whole issue is exacerbated by the resounding absence of any Google security bugs in the same database. One would assume that the only thing better than outing your competitors bugs is showing how well you fixed your own. Unless you subscribe to the ludicrous notion that somewhere software exists with zero bugs.

Testing is not about “outing” bugs as an act designed to extort fixes or embarrass your competition because let’s face it Google, you are giving the finger not to Microsoft but to Windows users when you publicize a bug that the fix is not entirely ready for.

Will this encourage speedier solutions or compromises in testing and deploying the bug fix? Won’t the compromises just lead to regression issues? The goal shifts from fix the bugs to fix the bugs in time and not in a good way.

So come on Google, it’s time to remember that with great power comes great responsibility. Don’t be that guy.

It’s time to reexamine the paradigm for Project Zero and realize that every time Google publicizes one of these bugs they become part of the problem, not the solution.

Google Project Zero - With Great Power

Comic cover art and quote with thanks to the incredible Marvel Comics

As a tester and a consumer, I may not be pleased to learn that Microsoft hasn’t patched these issues yet but I’m seriously <redacted> at Google over this. There are lessons here for Google and Microsoft that clearly need learning.

Google should continue to test for security issues but if you are going to threaten others with a ticking clock shouldn’t the time frame match a real estimate of how long it would take to develop, test and deploy the fix? I doubt that all bug fixes at Google receive the same arbitrary timeframe.

How about you? Do you think Google needs to dial it back for the sake of the consumer?