Upload VuGen Scripts
This topic describes how to upload VuGen scripts to Performance Center.
How to upload VuGen scripts to Performance Center
To upload VuGen scripts to Performance Center:
Create scripts in VuGen. For details, see the Virtual User Generator Help Center.For Service Virtualization:
If your test requires the service to be running while you record your business process, open Service Virtualization simultaneously and deploy the virtualized service. Record the script as usual.
Pointing calls to virtual services in the application under test covers two major scenarios:
Application components that use the service are embedded in the code or in a configuration file. In this case, update the code in the application under test or update the configuration file to point to the new URL.
A .NET Desktop application uses a web service, and the URL is set using a constant:
stringURL = http://hpe.com
A service or back-end component uses the web service and the URL is configured in the app.config file.
The service is consumed by accessing UDDI or some other registry component (Systinet) and the URL is retrieved at runtime. In this case, update the end point URL in UDDI/Systinet.
- Save the VuGen scripts locally. The scripts must be saved in ZIP format and must include all the files in the test scripts folder.
- On the My Performance Center navigation bar, select Test Management > Test Plan.
Click the Upload Scripts button.
Select a destination folder, scripts to upload, and upload options.
For user interface details, see Upload Scripts Dialog Box.
For details about uploading Vuser scripts from VuGen to ALM, see the section about saving VuGen scripts to ALM in the LoadRunner Help Center.
If you have a slow connection from VuGen or Analysis to ALM, this may be because the VuGen or Analysis machine does not have access to the WAN, and so cannot verify the digital signature of the relevant files.
Download and import the certificates from https://support.globalsign.com/customer/portal/articles/1426602-globalsign-root-certificates using certmgr MMC until the issue is resolved (you might not need to import all the certificates). This information is also available in knowledge base article KM02896928.