The Indianapolis Workshops on Software Testing (IWST) are an ongoing series of invitation-only, no-cost workshops for experienced software testers and related professionals. IWST strives to builds skills in software testing and allows people who are interested in topics in software testing to network with their peers. The emphasis is on mutual learning, sharing hands-on experiences and solving practical problems. In these monthly meetings, experienced working practitioners discuss pertinent state-of-the-art topics. IWST has been organized by a small team of local practitioners in the field of software testing.


Discussion from the problem solving opportunity presented by Marc during the February workshop. These ideas are the collective suggestions of Jason Halla, Marc Labranche, Denise Autry, Charlie Audritsh, John McConda, Andrew Andrada, Dana Spears, Michael Kelly, and Kurt McKain.

Possible Solutions:

1) User Acceptance Testing
- Share the risk and testing among the users
- User logic software needs to get "certified as compatible" with each new release

2) Dummy Applications (much like webserver testing using Java Pet Store)
- This would be used to establish an upper limit on idle.

3) Real world performance metrics (beta testing)

4) Artificial limit on idle
- This would be used to establish a lower limit on idle.

5) Measure user idle
- Does not sound like this can be technically accomplished given current tool(s)/configuration(s)
- This would be similar to "traditional" performance testing

Attendees of the February workshop please update the list of solutions as necessary. If one of the solutions was your suggestion, please ensure your intent was fully and accurately captured.


safe mode