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.
Monday, September 29, 2008
Ten Current Note-worthy Trends in the Application of Technology in Software Test Engineering
On September 27th 2008, at Microsoft (Gachibowli-Hyderabad-India), HYSEA Products' forum has conducted an excellent event on Software Product Testing. HYSEA is a great blessing to Hyderabad IT industry and beyond.
I have given a seminar on "Ten Current Note-worthy Trends in the Application of Technology in Software Test Engineering".
Some 400 attendees made their presence and I was deeply excited about having such a very focused event on Software Testing (first such thing in Hyderabad I guess, other than the seminars I have given in other events that were not necessarily only for testing).
Ramesh Loganathan (MD, Progress Software India) has invested interest and energy to make the event happen. Speakers from different Hyderabad based companies gave nice presentations on various topics.
I spoke for an hour (please see the below presentation) sharing my opinions on how currently technology is being used in test engineering. I ended my talk contemplating why we cannot have an aviation-style black-box as a part of software black-box testing so that the problem of irreproducible bugs is more seriously addressed at the source. There is a note from Microsoft sharing the very same viewpoint, published on September 29th 2008. VMWare has a feature of this sort in its world, and it is a good news that the Windows OS itself will have it soon through Visual Studio, making it more real.
I have given a seminar on "Ten Current Note-worthy Trends in the Application of Technology in Software Test Engineering".
Some 400 attendees made their presence and I was deeply excited about having such a very focused event on Software Testing (first such thing in Hyderabad I guess, other than the seminars I have given in other events that were not necessarily only for testing).
Ramesh Loganathan (MD, Progress Software India) has invested interest and energy to make the event happen. Speakers from different Hyderabad based companies gave nice presentations on various topics.
I spoke for an hour (please see the below presentation) sharing my opinions on how currently technology is being used in test engineering. I ended my talk contemplating why we cannot have an aviation-style black-box as a part of software black-box testing so that the problem of irreproducible bugs is more seriously addressed at the source. There is a note from Microsoft sharing the very same viewpoint, published on September 29th 2008. VMWare has a feature of this sort in its world, and it is a good news that the Windows OS itself will have it soon through Visual Studio, making it more real.
The presentation
As good as it gets!
Subscribe to:
Posts (Atom)