Feeds

Who classifies the bugs?

Management tricks that work for developers

Choosing a cloud hosting partner with confidence

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. ®

Top 5 reasons to deploy VMware with Tegile

More from The Register

next story
Euro Parliament VOTES to BREAK UP GOOGLE. Er, OK then
It CANNA do it, captain.They DON'T have the POWER!
Download alert: Nearly ALL top 100 Android, iOS paid apps hacked
Attack of the Clones? Yeah, but much, much scarier – report
NSA SOURCE CODE LEAK: Information slurp tools to appear online
Now you can run your own intelligence agency
Post-Microsoft, post-PC programming: The portable REVOLUTION
Code jockeys: count up and grab your fabulous tablets
Twitter App Graph exposes smartphone spyware feature
You don't want everyone to compile app lists from your fondleware? BAD LUCK
Microsoft adds video offering to Office 365. Oh NOES, you'll need Adobe Flash
Lovely presentations... but not on your Flash-hating mobe
prev story

Whitepapers

10 ways wire data helps conquer IT complexity
IT teams can automatically detect problems across the IT environment, spot data theft, select unique pieces of transaction payloads to send to a data source, and more.
Getting started with customer-focused identity management
Learn why identity is a fundamental requirement to digital growth, and how without it there is no way to identify and engage customers in a meaningful way.
The total economic impact of Druva inSync
Examining the ROI enterprises may realize by implementing inSync, as they look to improve backup and recovery of endpoint data in a cost-effective manner.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Beginner's guide to SSL certificates
De-mystify the technology involved and give you the information you need to make the best decision when considering your online security options.