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 20
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 Te
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.
On Friday, 12 June 2015 13:49:53 UTC+1, Mark Waite wrote:
>
> I expect it is doable, though probably easiest if y
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?
On Fri, Jun 12, 2015 at 5:49 AM Mark Waite
wrote:
> I expect it is doable, though probably easiest if you assure that the
> Jenkins node which is executi
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 run
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 MST
