Anne-Marie Charret has posted about her desire to keep test documents when doing Exploratory testing.

On my current project we are delivering in excess of three thousand requirements, and with each requirement spawning up to six test cases, we were simply drowning in a sea of tests.

To try and survive this, and complete the project with my sanity intact, something had to change. There were a lot of changes, however the main change that I instigated was to introduce the option of performing exploratory testing when the requirement was delivered. Documenting the tests as we performed them, instead of a huge up-front planning process. This ensures that we still maintain a record of our test case to requirement traceability

Well did it work? I am happy to say, yes. Instead of spending most of our time in front of Microsoft Team Foundation Server, we spent the time in front of the application finding bugs.

With Microsoft robotics studio around these days a lot of guys are now playing with various kinds of robots, including some guys that I have worked with. Rob is playing around with a Lego Mindstorms robot and Dan has been working with a KHR2HV.

Well I am not about to start shouting me too. My brother and I have been working on a completely different type of “robot” that is currently controlled by DOS based software.

If you are curious what this is going to be used for you can head over to my other blog and see the details.

Need to do browser compatibility testing for IE 5.5, 6, 8 and 8 ?

IeTester should do the trick. It’s a stand alone application that contains all 4 rendering engines.