Issue Description:
We have release definitions set up to execute Coded UI test cases, the test agent deployment task has run into an issue where in it the execution does not end until the deployment is manually cancelled, the message displayed on the terminal is as follows "DistributedTests: Task 'ConfigureTestAgent' on machine 'HOSTNAME:5985' is taking time. Please Wait"
vsts_testagent.exe path is supplied from local path.
Environment Details:
TFS on-premises , TFS 2017 15.112.26307.0 (Tfs2017.Update1)
Build Agent : Private, OS: Windows Server 2012 R2, build agent version : 2.112.0
Test Agent : Private, OS: Windows 10
Test deployment task version: vstf_testagent.exe version version 14.0.23107.10
Test agent deployment step will spend longer time when the first time to deploy the test agents on a machine, if a server has been deployed successfully before, it would be much faster.
Please try below items to fix that:
Try with same credentials for build agent and test agent.
Try to download the test agent and install it on that machine manually, then try to queue build with the test agent deployment taskagain. (Install and configure test agents)
Try to deploy the test agent on another clean test machine.
Similar issue in Github for your reference: https://github.com/Microsoft/vsts-tasks/issues/2023
Related
1.We develop code in eclipse
2.Integrate it with jenkins
3.Store codes on github
4.integrate jenkins and github
5. Jenkins triggers test scripts from github
Now my questions are this
1. Where exactly the tests run in realtime on scheduled basis ?
2. Jenkins has to run 24/7 in company server so it triggers test scripts in one of company's computer ?
Jenkins run the test on either master or slave machine which you configure.
Example:
yes.
I'm trying out DevOps with VSTS, Docker and Java and I'm stuck with failing builds PFA screenshots of the same.
VSTS build failing while Queue Jenkins job task
Job is successfully executed on Jenkins and .War file is also produced.
This has been setup on Azure following document
https://github.com/msdevno/hol-oss-devops
Another approach is to have the commit to VSTS trigger the build in Jenkins. Then have Jenkins trigger the release in VSTS. Setting up CI/CD with the TFS Plugin for Jenkins This would not require using VSTS for build.
I was able to resolve the above issue.
My guess worked out correct.
Changing the Public IP from Dynamic to Static caused this issue.
Looked into Jenkins configuration(Manange Jenkins > Configure System > Jenkins Location > Jenkins URL) This was containing dynamic IP and now I've changed it to new static IP and voila it works fine. Build Succeeds and status updated on VSTS as well :)
Thanks for sparing your time in looking to my issue #Starain-MSFT & #Donovan
As per the documentation, in order to run Coded-UI as part of the build you need to have your build agent running as interactive Mode (Not as a service) also your Test Agent need to be deployed as Interactive Mode.
Now the problem is when you deploy your test agent your build machine will restart automatically so your Build agent will not restart cause its not a a service.
How can you work around this ?
Two options:
Don't use the build server as a test agent. Depending on the complexity and size of the test suite, you can either run the tests directly on the deployed environment or have a dedicated group of test machines to parallelize the run.
Install the test agent outside of a build process and just use the "run functional tests" task to connect to the already-running agent. The "Install test agent" task is really for scenarios closer to option #1, especially if you're doing things like provisioning test machines in the cloud on-demand.
Since you would like to run Coded UI test, you have to configure the test agent to interact with the Desktop and build agent running as interactive Mode.
If you insist on installing the TFS Test agent on the same machine as the Build agent. You need to manually install and configure the agents first. Then specify the test agent installation media path in test agent deploy task and use Run Functional Test task to run Automated Test on agent machine.
I am scheduling QTP scripts using Jenkins, intended to run on weekends. The QTP scripts are in the same Jenkins machines.
The build is not triggered at the scheduled time instead it triggers only when I login to the VM as it seems so.
Configuration:
OS : Windows 7 Ultimate
Jenkins version: 1.620 (master only)
When I do build manually, it works. Only the scheduling is not working.
If you are running Jenkins Slave as a service, you have to make sure that it runs as administrator in services.msc in the Log On tab. Make sure to restart the service after you add the Admin Account.
Cheers!
I am running UFT Test Suite manually on the host machine, however i now have the requirement to run the smoke tests as soon as the new build is delivered in jenkins. For that i need to run the test suite automatically using Jenkings. Can someone help me in the direction, how this can be achieved? I have never used Jenkins before.
Looks like theres a plugin for Jenkins which enables integration with HP UFT. Take a look at the Jenkins wiki page for instructions about how to install and use it.
As you didn't mention that you are using ALM so I am assuming that you have some kind of driver script in vbs which runs your test suite. You do not necessarily require any plugin in jenkins to run your UFT suite(however you can also check the suggestion given in the previous answer). Create a job in jenkins and call your vbs file (driver file) or a bat file which kicks off your execution your test machine.
Your test execution machine can be configured as jenkins slave. Only thing which you need to take care off is to remove the settings which can let go your jenkins slave machine which is your uft execution machine in standby mode or locked user mode(uft scripts will fail otherwise). You can handle this by configuring windows settings(if admin allows) or by using some small scripts to move mouse after some intervals.
Your test execution job in jenkins(master) machine can be made dependent on the job which goes to success when new build is available. As soon as new build is available - that job goes to success then your Test job gets notified and connects to UFT execution machine(slave) and starts running your test.
I am trying to integrate ALM with jenkins but not working
Started by user admin
Running as SYSTEM
Building in workspace C:\JENKINSHOME\workspace\CLRP_AUTO_RN
[CLRP_AUTO_RN] $ C:\JENKINSHOME\workspace\CLRP_AUTO_RN\HpToolsLauncher.exe -paramfile props05092020010832244.txt
"Started..."
Timeout is set to: -1
Run mode is set to: RUN_PLANNED_HOST
Unable to retrieve test set folder: Node not found.
Node not found.
Starting test set execution
Test set name: CLRP Smoke Test Automation Run, Test set id: 104
Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://almserver:8080/qcbin/TDConnectivity_index.html
Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE
Finished: FAILURE