Friday, May 12, 2017 08:15
This is a tricky question and the correct answer depends on what you want to achieve. I have assumed that you want to have an archive of the test scripts that ran against a particular Jenkins build stored with the other test artefacts associated with that build (such as test results and so on).
I haven’t used TFS with Jenkins but I have some experience of integrating LoadRunner and Performance Center tests with Jenkins as well as using Jenkins to control powershell scripts on remote servers and copy files to and from servers after tests. I’d recommend the following:
1. Create a Jenkins build job that checks for some sort of status update in TFS (using the TFS plugin for Jenkins). This could detect a “commit” of code or a deployment.
2. Create your initial performance test in LoadRunner which runs after step 1. Assuming that this test passes, you’ll have test results from that test copied into your Jenkins workspace.
3. Use the “PowerShell” plugin to zip the contents of your scripts folder into a file on the LoadRunner PC. You should “timestamp” this so you can associate it with the test that ran at the same time.
4. Use the Jenkins Plugin “Copy to Slave” to copy the zipped up scripts to your Jenkins Workspace.
5. Run your larger scale Performance Center under Jenkins control.
6. Use the TFS plugin to copy any test artefacts from the workspace that you wish to associate with your specific build.
Apart from steps 1 and 6, I’ve done all of the above. If anybody reading this has TFS experience that could give some TFS-specific advice, it would be great if they could contribute to this discussion.