But also be careful not to oversimplify your tests. If for example testing focuses on Incident Management, one transaction would normally be new incident creation and test would need to create a valid new incident regardless of the type of testing. Running concurrent ITSM transactions does not mean that sending static HTTP requests (hard coded data) will be sufficient as this would most likely generate a significant number of application level errors clouding the overall performance picture (to continue with the old fashioned use of the word :). Tests transactions also need to be valid for things like automatic ticket assignment or SLA (in my incident creation example) to be invoked correctly making test results more relevant.
Choice of testing tool should not drive testing requirements and it is best to start with what is required outcome of the testing and only then look at the tooling. While it may be possible to use a generic HTTP testing tool to load test Mid Tier, data encoding and AR specific response validation complicate things quite significantly. Things are much better with one of the AR specific web testing tools that can handle ITSM Back Channel calls seamlessly and choice there is Scapa TPP or Silk. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
