I think one of the important things to consider when doing user testing is to get as much prod data into the "main" ITSM tables like Incident, Task, Work Info, etc... That way, the testing can account for all the table refreshes that are done on things like the Incident Management and Overview Consoles.
On Thu, Jan 19, 2012 at 4:49 PM, patchsk <vamsi...@gmail.com> wrote: > ** We went through the same hurdle when we were upgrading to ITSM 7.6.03. > We use HP tools internally for load testing and it did not completely work > with remedy. It could record only logins/non-ITSM form updates/logouts. > So we are left with either buying a third party tools for which we do not > have budget allocated or build something internally. > Since it is an OOTB vendor product our QA team was not much demanding > about load/performance testing. > But to our own due diligence and go get some kind of confidence about our > infrastructure we built some simple webservices/java apis/remedy > escalations to create/update several entries and just observed how many > tickets created/updated per min etc.. > Agree it is not a perfect load balancing but with the given resources we > went with that. > Then we had several users login to remedy at the same time and do some > kind of testing for an hour and get their inputs. > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > -- *Tauf Chowdhury * _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
