Comments on: Why Is Testing Taking So Long? (Part 1)

By: soubhik

soubhik — Wed, 02 Nov 2011 15:00:36 +0000

i m into performance testing and working in a comparatively large project. The test coverage is so baad that we end up running 3 to 4 - 12 hr tests a month. Michael replies: That's a test result. Main reasons behind thus being the large number of opened and reopened QCs.. which always delays the scripting until the las week of release schedule... That's a test result too. The puzzle for me is why people ignore these test results.

By: Monirul Islam

Monirul Islam — Thu, 11 Aug 2011 04:02:04 +0000

I am working with team D, E, F… I tried to understand my management that if your developers throw rubbish, what can I do?

Michael replies: I’d encourage management to read the blog post to which you’re referring. Print it out, if you like.

In the end, though, managers are often reluctant to put quality requirements on programmers. The mission is “produce code”, rather than “produce code that works”. I think the best that we can do is to underscore the cost, in time and effort, associated with sloppy code. Sometimes we can discuss that with a programmer who can help to transmit the message, since usually the programmers are under time pressure, rather than quality pressure. In my experience, many programmers don’t like that either. Do you have any friends—even one or two—among the programmers with whom you might align?

But the good thing is the length of my micro-sessions is reducing day by day.

If your microsessions are getting shorter because you’ve improved your skill at investigating and reporting quickly, or because the programmers have helped in making the products easier to test, then that’s probably all to the good. On the other hand, if your sessions are shorter because you’re reducing your coverage, that might not be such a good thing. Let’s be careful out there.

By: Creating a Test Management Super Class | thoughts from the test eye

Creating a Test Management Super Class | thoughts from the test eye — Sat, 29 May 2010 19:53:24 +0000

[...] test to non-testers: Why are we not QA, why does it take so much time? Why do developers need to test as well. What is our goal as testers. What responsibilities do we [...]

By: Utopic estimations in testing | thoughts from the test eye

Utopic estimations in testing | thoughts from the test eye — Thu, 13 May 2010 19:32:23 +0000

[...] http://www.developsense.com/blog/2009/11/why-is-testing-taking-so-long-part-1/ [...]

By: Sharath Byregowda

Sharath Byregowda — Fri, 27 Nov 2009 13:13:20 +0000

Michael, I really wonder if test managers have not figured this out till today, or do they know this but still want to control people rather than seeking value from them or need numbers to feed their bosses. It almost looks like a food chain

-Sharath.B

By: Stefan

Stefan — Wed, 25 Nov 2009 06:40:23 +0000

Lots of bugs means reduced coverage, or slower testing, or both.

I like the statement, short and right on spot...

By: vips

vips — Wed, 25 Nov 2009 06:23:00 +0000

I agree with you Michael, and it is really interesting to read the way you have presented this. Though the situations differ from team to team and a manager should understand those dynamics before measuring something

By: tom_griffin

tom_griffin — Tue, 24 Nov 2009 23:24:03 +0000

Thanks, I am working in a Team C environment and have been wondering why I can never seem to make much progress.