Comments for Software Testing and more

Comment on Execute testable specifications: Simulation Testing by website designer in meerut/ web designer in meerut/website designer in india /seo/ online business promoter/ web development company/ b2b business portal/

Wed, 01 Feb 2012 06:10:45 +0000

website designer in meerut/ web designer in meerut/website designer in india /seo/ online business promoter/ web development company/ b2b business portal/…

[...]Execute testable specifications: Simulation Testing :: Software Testing and more[...]…

Comment on 5 Reasons to start with Agile Testing by Andreas

Andreas — Mon, 23 Jan 2012 12:34:06 +0000

Manish,

Thanks for your comment. However these reasons are valid, there are a lot of companies that think that Agile will solve all their problems. The fun is starting with Agile in these organisations shows a lot of impediments. Improving these will help organisations go forward!

Comment on Agile is not the answer by Bob Hartman

Bob Hartman — Sun, 22 Jan 2012 00:01:54 +0000

I’m confused why you think agile isn’t dramatically better given the two graphs you show. Assume just a single bug shows up in each phase (I won’t get into why agile won’t have phases, let’s just take your data at face value). In the waterfall approach it appears you will have a bug during design, code, test, acceptance and production. Roughly looking at your graph it will cost 5 to fix the bug in design, 10 to fix in the one in code, 20 to fix the one in test, 50 to fix the one in acceptance and 100 to fix the one in production for a total of 185 cost units.

In agile the phases are similar and the cost to fix a bug in each phase is basically zero until we get to test and production. At this points it costs 10 to fix something in test and 100 to fix something in production. That is a total of 110 cost units to fix a bug occurring at each level. Is not agile 40% lower in cost? And that percentage rises as more things are found earlier than production in the process.

If we instead assume a decrease of errors along the way, perhaps 10 in the earliest phase, then 7, then 5, 3 and 1 the numbers get crazy. In waterfall you would spend 7×5+5×10+3×20+2×45+1×100=335 cost units. In agile you would spend 7×1+5×1+3×1+2×10+1×100=120 cost units. Far, far less expensive.

To me these graphs show very clearly that agile IS the answer. What am I missing?

Comment on The W-Model by Ewald Roodenrijs

Ewald Roodenrijs — Thu, 19 Jan 2012 04:50:15 +0000

Preethi,

Thanks.

-Ewald

Comment on Agile is not the answer by Ewald Roodenrijs

Ewald Roodenrijs — Thu, 19 Jan 2012 04:49:34 +0000

Curtis,

Yes, Agile advices that. But I don’t see it enough. It’s still difficult to implement. But it’s not about the title only, it’s about cost saving with agile compared to waterfall. I don’t think agile is different from waterfall on automated testing. Why can’t I do that in waterfall? The thing you can say, as you are, it forces you more to automate as you do short cycle testing where automation supports you in most ways, but if I’m disciplined enough I can do the same at waterfall.

Thanks for your comment.

-Ewald

Comment on When does testing stop? by Ewald Roodenrijs

Ewald Roodenrijs — Thu, 19 Jan 2012 04:45:54 +0000

Julie,

Depends on how the contract is made up. But yeas, that’s a good economic option. You say we test x amount of cycles and then you’re finished.

-Ewald

Comment on Cloud Applications; testing on the cloud by Michiel van Otegem

Michiel van Otegem — Wed, 18 Jan 2012 10:01:40 +0000

Integration is one of the biggest challenges for the cloud. Between cloud applications and applications in the client’s network, but as more and more moves to the cloud between clud applications from different suppliers. At the foundation this means that identity must work across all providers (so devs and testers should wrap their heads around WS-Federation, OAuth, OpenID etc.). Only when that’s taken care of properly can you look at functional integration. What we need there are standards that not only enable you to (dynamically) discover services, but also dynamically integrate functionality without additional coding.

Comment on When does testing stop? by software testing tool

software testing tool — Tue, 17 Jan 2012 13:52:27 +0000

I suppose if you can define a number of testing cycles and then deliver the product to your client who will then test it on his own and let you know if he has spotted any bugs ?

Comment on Stop the insanity in software testing! by Business Quality with PointZERO; A next step in QA & Testing :: Software Testing and more

Mon, 16 Jan 2012 06:01:53 +0000

[...] the same thing over and over again and expecting different results”. I already said this in an earlier post, but it also fits here perfectly. And we’re being insane in IT quality today. Every year, money [...]

Comment on Agile is not the answer by Curtis Yanko

Curtis Yanko — Thu, 12 Jan 2012 23:12:06 +0000

How is Agile not the answer? If anything it IS the answer. Agile requires you do the testing in iteration which forces you to do automated testing which in turn drives down it’s cost and increases it’s efficacy.