What I write here is not about a feature of www.testersdesk.com.
In some complex UI web applications where there are chains of events that happen on a SINGLE button (or button-like) click, it is very possible that a request is submitted twice (or more) resulting in the server side process to be triggered twice. For a normal tester, this is an easy catch if it is a update/insert request because he/she can detect the effect. But if it is a selection of records which produces the same output for any number of requests, how would the tester know how many requests were sent?
Welcome to technology applied in software testing. I do not bother who does this (developer/tester/manager/vice-president/ceo/cfo/cto) but someone has to use a proxy server to see the outgoing requests.
It is always we humans who can find issues, but in the process technology must to be used as a helper to accomplish the objective.
Friday, October 24, 2008
My interactions with Pradeep Soundararajan and Shrini Kulkarni at Test2008
Having had met Pradeep and Shrini at Test2008 conference, I wanted to externalize a small extract from our conversations.
Firstly, I would say the readers of their blogs are lucky for getting the insights and influential thoughts so really needed to ensure value to the customers.
I had a quick overview from Shrini on the schools of thought in testing. I never knew the concept of Schools of thought in Testing, but having looked at the principles stated in http://www.context-driven-testing.com/, it made a lot of sense as to what I have been thinking/living all the time, and for a good thinker the word 'context' itself explains all about it.
I liked the way how Pradeep has explained the term "bug free software" -> software delivered with free bugs:-) I think there is a post on this topic in his blog too that I visited yesterday.
Overall, It brings me in to a deep introspection, as well as do some serious planning around how we can perform value-assurance (a synonym I use for the word 'testing') to testers through TestersDesk.com. Obviously, a testing product itself cannot have bugs and needs to serve as an example for having reasonable quality and deliver the value to testers. We exist to exploit technology in whatever ways possible, basically offloading the mundane tasks of a typical test engineer, and have now got more careful at what we build.
I am posting this to highlight the fact that it was an intellectually stimulating hour talking to Pradeep and Shrini, and I thank Pradeep for nominating TestersDesk.com for the Thought Leadership Award at Test2008.
Firstly, I would say the readers of their blogs are lucky for getting the insights and influential thoughts so really needed to ensure value to the customers.
I had a quick overview from Shrini on the schools of thought in testing. I never knew the concept of Schools of thought in Testing, but having looked at the principles stated in http://www.context-driven-testing.com/, it made a lot of sense as to what I have been thinking/living all the time, and for a good thinker the word 'context' itself explains all about it.
I liked the way how Pradeep has explained the term "bug free software" -> software delivered with free bugs:-) I think there is a post on this topic in his blog too that I visited yesterday.
Overall, It brings me in to a deep introspection, as well as do some serious planning around how we can perform value-assurance (a synonym I use for the word 'testing') to testers through TestersDesk.com. Obviously, a testing product itself cannot have bugs and needs to serve as an example for having reasonable quality and deliver the value to testers. We exist to exploit technology in whatever ways possible, basically offloading the mundane tasks of a typical test engineer, and have now got more careful at what we build.
I am posting this to highlight the fact that it was an intellectually stimulating hour talking to Pradeep and Shrini, and I thank Pradeep for nominating TestersDesk.com for the Thought Leadership Award at Test2008.
Subscribe to:
Posts (Atom)