Feeds

Who classifies the bugs?

Management tricks that work for developers

High performance access to file storage

I enjoyed Mary Branscombe's piece on Adobe development practices (here).

However, one point that occurred to me (after a misspent past life in software QA) is how do you stop coders marking bugs as closed (or reclassifying them as "features" or "enhancement requests") in order to get back to the fun stuff? How much power does QE (Quality Engineering) have in this Adobe development environment?

So, Mary asked Russell Williams of Adobe just these questions.

QE has quite a lot of power it seems (as I'd expect): "[Coders] don't get an unqualified decision on that – 'as designed' has to be accepted by both the development engineer and QE, though only the QE can mark a bug closed," he says.

However, in practice, it's not quite as simple as that: "One accounting trick that was used was to temporarily distribute some of the bugs from somebody who was over their limit to somebody with a lower bug count," Russell says. "Another thing we did was more of a workload management thing. As a milestone approached where more stringent bug criteria were going to be applied, developers started shifting workload to QE by being more eager to bounce bugs back with 'needs more info'. This moved more of the bug isolation work onto the QEs and let the developers focus on bugs they could easily reproduce; those are much easier to fix."

Mary rather likes the idea of "tricks that actually work", and so do I, but (as usual) I only see them working in a reasonably mature organisation, with well-informed and sophisticated project management.

I note that Russell is well aware of when workload shifts from coders to QA, which is probably a good sign of organisational maturity. After all, if QE is trying to reproduce low-level coding bugs (as might happen in a less mature organisation), it's not getting on with its most important role (in my opinion), of checking the "fitness for purpose" of the whole system, in business terms. ®

High performance access to file storage

More from The Register

next story
Windows 8.1, which you probably haven't upgraded to yet, ALREADY OBSOLETE
Pre-Update versions of new Windows version will no longer support patches
Android engineer: We DIDN'T copy Apple OR follow Samsung's orders
Veep testifies for Samsung during Apple patent trial
OpenSSL Heartbleed: Bloody nose for open-source bleeding hearts
Bloke behind the cockup says not enough people are helping crucial crypto project
Microsoft lobs pre-release Windows Phone 8.1 at devs who dare
App makers can load it before anyone else, but if they do they're stuck with it
Half of Twitter's 'active users' are SILENT STALKERS
Nearly 50% have NEVER tweeted a word
Windows XP still has 27 per cent market share on its deathbed
Windows 7 making some gains on XP Death Day
Internet-of-stuff startup dumps NoSQL for ... SQL?
NoSQL taste great at first but lacks proper nutrients, says startup cloud whiz
US taxman blows Win XP deadline, must now spend millions on custom support
Gov't IT likened to 'a Model T with a lot of things on top of it'
This time it's 'Personal': new Office 365 sub covers just two devices
Redmond also brings Office into Google's back yard
prev story

Whitepapers

Securing web applications made simple and scalable
In this whitepaper learn how automated security testing can provide a simple and scalable way to protect your web applications.
Five 3D headsets to be won!
We were so impressed by the Durovis Dive headset we’ve asked the company to give some away to Reg readers.
HP ArcSight ESM solution helps Finansbank
Based on their experience using HP ArcSight Enterprise Security Manager for IT security operations, Finansbank moved to HP ArcSight ESM for fraud management.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Mobile application security study
Download this report to see the alarming realities regarding the sheer number of applications vulnerable to attack, as well as the most common and easily addressable vulnerability errors.