Comments on: How would you test this?

By: Testing The Limits With Matt Heusser (part 1) | Software Testing Blog

Testing The Limits With Matt Heusser (part 1) | Software Testing Blog — Mon, 30 Nov 2009 16:21:30 +0000

[...] of “Testing The Limits”, we sit down with Matt Heusser (@mheusser) — prolific blogger for STPCollaborative, thought leader and testing extraordinaire. We’ll discuss the state of software testing, [...]

By: How I’d Test it – Re: Matt Heusser’s Challenge « Testing with a Chainsaw

Tue, 13 Oct 2009 19:25:51 +0000

[...] tiresome to read a lot of theory without some context and examples. Matt Heusser’s recent testing challenge is an opportunity for tester’s to show how they think they would test a specific item. Matt [...]

By: Joe Harter

Joe Harter — Mon, 12 Oct 2009 03:18:01 +0000

Thanks for the challenge Matt! I posted my response on my blog. I’d love to hear your thoughts (as always)!

- Joe

http://joeharterqa.wordpress.com/2009/10/11/how-id-test-it-re-matt-heussers-challenge/

By: How I would test this – Part II – The refinement « shino.de

How I would test this – Part II – The refinement « shino.de — Wed, 07 Oct 2009 19:49:06 +0000

[...] having proposed the basic idea for Matthew Heusser’s latest testing challenge, I would like to present the refinement based on Matt’s answers. Additionally I would like to [...]

By: Marlena’s Blog » Blog Archive » Testing a Social Web App Part 2: Test Plan and Strategy

Wed, 07 Oct 2009 02:10:11 +0000

[...] the previous post, I discussed the app in Matt Heusser’s latest test challenge and questions I asked about it. In this post, I will show my overall test strategy and plan. I [...]

By: Marlena’s Blog » Blog Archive » Testing a Social Web App Part 1: Questions

Wed, 07 Oct 2009 01:54:14 +0000

[...] Heusser recently posted a testing challenge on his blog. The challenge is to create a test plan and strategy for the Socialtext’s [...]

By: Markus Gärtner

Markus Gärtner — Fri, 02 Oct 2009 18:57:30 +0000

There are some questions open for me to make a more informed decision about what might happen in the next two weeks to three months. Anyways I started to draft some basic ideas, that I would origin the approach on: http://blog.shino.de/2009/10/02/how-i-would-test-this-part-i-the-basic-idea/

By: How I would test this – Part I – The basic idea « shino.de

How I would test this – Part I – The basic idea « shino.de — Fri, 02 Oct 2009 18:55:26 +0000

[...] Heusser from time to time comes up with challenges related to testing. The latest one introduces a web application and asks for a strategy to stress it out. Here is my (late) reponse to [...]

By: Bruce Rennie

Bruce Rennie — Fri, 02 Oct 2009 01:36:47 +0000

If it’s an application like twitter, myspace, or facebook, you probably want the freedom to update anytime you need to, as soon as you need to, regardless of how many users are currently online. And, as they say, if you want to become good at something, do it all the time. That seems to indicate that you should try to push updates once it’s cleared your continuous build.

Sounds scary, but there are a couple of obvious advantages to doing this. First, if you can go a couple of weeks of pushing CI builds out without breaking something then you can say that you’re ready to handle a live rollout. Plus, nothing like the possibility of busting the company wiki and having the CEO give you the evil eye to encourage people to think twice before committing that change.

Crank it to 11.

By: Bruce Rennie

Bruce Rennie — Thu, 01 Oct 2009 23:37:50 +0000

5 second answer:

Since it’s a wiki, I’d get the team to eat their own dog food by using it for a project repository: story details, planning notes, discussions, etc. Hell, get the entire company to use it.

Cheers,
/bruce

[and we do! (You're onto me, as they say. Would you have them use the daily build do to it, and update it every day? Or continuous build?]