I recently completed a client assignment where I was asked to help plan an upgrade of HP ALM to allow the integration of ALM and Performance Center. As part of the assignment, I sat down with the performance testers and discussed the implications of moving from LoadRunner to Performance Center.
Over the next few weeks, I'll be publishing a series of articles and tips that potentially all testers should follow; both because they represent good practice and because they may help to facilitate any future migration from LoadRunner to Performance Center. Inthis first article, I discuss test data.
Because Performance Center allocates load generators at runtime, you can’t (easily) use local test data files like you can in LoadRunner. Here are my recommendations.
- Modify scripts to use UNC paths, rather than local file paths for test data.
e.g. C:\TestData\Name.dat should be \\Servername\Sharename\ProjectName\TestData\Name.dat
Alternatively, use VTS for some test data if appropriate.
Add a test data script. One suggestion, that I hadn’t heard of before is to upload a script to the project called, calling it, for example “TestData”. This script can contain all the test data files that your scripts need and it will be accessible from the other scripts, since it will be stored in the same project. Other scripts can then access data in this script using relative paths. I want to try this out to confirm that it works but I can’t imagine why it wouldn’t.
Use relative paths for “include files” (if you have any) as well as test data.
The "include files" shown below are OK, because they are LR-specific files, if you have written your own custom libraries, it may be sensible to store them in a single place.
If you'd like to share your experiences of migrating to Performance Center, please share them at email@example.com or by adding to the comments below.