Automated MS CUIT (Coded UI Tests) with Jenkins

[David Periam]

We have a project that I have been asked to build and integrate an Automated CI, Deployment and Automated UI Tests for.

I have built a framework, using Visual Studio 2010 and Page Object Mapping; a number of MS Coded UI Tests (CUIT) have been created which work brilliantly when run with the MSTEST program.
The setup I hope to end up with is a CI server which will run the tests against a remote Web Instance, all from an IE instance on the server against the Web Instance of our Web application.

We are in the process of trialling Jenkins to see if that can help in my task;

I have a server, running Jenkins ver. 1.616 as of 12th June 2015.

I have hit a stumbling block in that I am unable to get Jenkins to run Automated MS Coded UI Tests against.

Can anyone advise: is this doable and if it is, how should I go about finishing this last all important step to finish our CI environment?

Many thanks, Dave

[Mark Waite]

I expect it is doable, though probably easiest if you assure that the Jenkins node which is executing those tests is not running as a service.  Running tests which drive a web browser from a service will likely be more challenging than allowing those coded UI tests to be run from a Jenkins slave running on the desktop.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d8719300-c7f8-447d-923c-e401660a39fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Slide]

It would be helpful to understand what is not working with the UI tests as well. Do you get an error? Any logs that might help show the issue?

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFiD-0GFiUNnR3Dc46pzx9ncf%3DKQL4w7EKch5XSgef_aA%40mail.gmail.com.

[David Periam]

Mark,

The current setup is that Jenkins is running as a service.
I will take a look into not running Jenkins as a service to see if this helps.

Many thanks for your time with this.

[David Periam]

Slide,

The console output for the job is:

mstest /testContainer:******.dll /test:******
Microsoft (R) Test Execution Command Line Tool Version 10.0.30319.1
Copyright (c) Microsoft Corporation. All rights reserved.
   
Loading *****.dll...
Starting execution...

Results               Top Level Tests
-------               ---------------
Failed                ******
0/1 test(s) Passed, 1 Failed

Results               ******
-------               -------------------------
Failed                ******
0/1 test(s) Passed, 1 Failed

Summary
-------
Test Run Failed.
  Failed  2
  ---------
  Total   2
Results file:  c:\Jenkins-CI\******\Releases\forTesting\******\bin\TestResults\SYSTEM 2015-06-10 14_41_40.trx
Test Settings: Default Test Settings
Finished: SUCCESS


If there are any other log files that you can tell me about with regards to Jenkins that could help, please let me know and I'll make them available.

Thank you for your time.

[David Periam]

Mark,

To confirm: I have run Jenkins from the command line and re-run the automated build and cuit test setup.
The outcome is the same as I have mentioned previously -- the code builds but the cuit (coded ui test) fails.

Would you have anything to add?

Many Thanks, Dave.

On Friday, 12 June 2015 13:49:53 UTC+1, Mark Waite wrote: