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.
No comments:
Post a Comment