Comments on: Premises of Rapid Software Testing, Part 1

By: Software Testing Carnival #1 — Hexawise

Software Testing Carnival #1 — Hexawise — Wed, 31 Oct 2012 13:36:26 +0000

[...] Premises of Rapid Software Testing part 1 (engagement with software development), part 2 (the nature of testing as an investigative activity) and part 3 (our relationship to our clients) by Michael Bolton – “1) Software projects and products are relationships between people, who are creatures both of emotion and rational thought… 4) A test is an activity; it is a performance, not an artifact… 6) We commit to performing credible, cost-effective testing, and we will inform our clients of anything that threatens that commitment.” [...]

By: Context Driven Testing » Censure people for disagreeing with us?

Context Driven Testing » Censure people for disagreeing with us? — Mon, 15 Oct 2012 03:09:46 +0000

[...] some of them feel intimidated. At this point, I think the list is more a collection of fans of Bach & Bolton’s Rapid Software Testing approach than of context-driven testing. Therefore, I do not think this group has the authority to [...]

By: bharani

bharani — Fri, 05 Oct 2012 06:29:54 +0000

I felt, by runthrough this article i have acquired good epistemology and i have pored what is happing in the Software Development. Really good point of your third step about Despite our Best hopes. Your words really hits my mind and started to think over it. How should i optimize and improve my testing activites and I learnt to be fanasty while testing the product. Thanks for beset of Elaboreted Rapid testing article.

By: nilanjan

nilanjan — Wed, 03 Oct 2012 09:55:04 +0000

For 3. ….some degree of inexperience, carelessness, and incompetence is normal…

are you referring to biases…not sure.

By: Running with the Red Queen « Yes, Broken…

Running with the Red Queen « Yes, Broken… — Tue, 02 Oct 2012 12:14:57 +0000

[...] the other morning, I came across Michael Bolton’s excellent articles on the premises of Rapid Software Testing (RST). RST is something that I’ve been keenly interested in, but haven’t had the [...]

By: John Stevenson

John Stevenson — Wed, 26 Sep 2012 12:21:42 +0000

Another great article Michael and I am looking forward to the rest of it.

Michael replies: Thanks, John.

You are making some really good points and the following especially is meaningful for me at the moment and within the craft of testing given the exposure the latest ISO software testing standard appears to be getting.

“Other testing and development methodologies seem to assume that everyone can and will do the right thing at the right time. We find that incredible. Any methodology that ignores human fallibility is a fantasy. By saying that human fallibility is normal, we’re not trying to defend it or apologize for it, but we are pointing out that we must expect to encounter it in ourselves and in others, to deal with it compassionately, and make the most of our opportunities to learn our craft and build our skills.”

I keep hearing the same questions time and time again.

When do you expect to finish testing?
What have you got left to test?
Why did you miss that?

That paragraph above sums up the why.

I hope you do not mind but I am going to ‘borrow’ that and use with the teams I work with.

You’re absolutely welcome to do that. That’s why I post this stuff.

There are answers to those questions.

1) “Since you’re in charge of the shipping decision, you’re also in charge of deciding whether you have enough information to make that decision. We could test forever, but you probably don’t want us to do that; you probably have a shipping date in mind. Let’s talk about what you’d like us to look at, and what we all think are risks worth considering, and we’ll work together to make sure you’re getting the information you need as it’s being revealed.”

2) I’d offer some of the ideas that I’ve offered before: http://www.developsense.com/publications.html#GotYouCovered, http://www.developsense.com/publications.html#CoverOrDiscover, http://www.developsense.com/publications.html#AMapByAnyOtherName.

3) “Do you mean ‘how did we all miss that?’ Here are some possible answers: http://www.developsense.com/blog/2011/01/youve-got-issues/“.

By: Five Blogs – 26 September 2012 « 5blogs

Five Blogs – 26 September 2012 « 5blogs — Wed, 26 Sep 2012 06:46:37 +0000

[...] Premises of Rapid Software Testing, Part 1 Written by: Michaael Bolton [...]

By: Geek Reading September 25, 2012 | Regular Geek

Geek Reading September 25, 2012 | Regular Geek — Tue, 25 Sep 2012 16:00:13 +0000

[...] Premises of Rapid Software Testing, Part 1 (Developsense Blog) [...]