Run UI Automation Testing

Fernando Nacpil March 10, 2016

The flow that I am thinking is that

 

  1. Check out source code
  2. Install dependencies  - bower
  3. Run the server in the agent (mvn tomcut:run)
  4. Run the Selenium test
  5. Turn off the server

But looking at the mvn tomcut:run, the CI will not stop as it feels like it runs the server on it self and we cannot proceed with the step 4. 

 

What's the best practice here?

 

 

2 answers

0 votes
ernestm March 11, 2016

I think setting maven.tomcat.fork to true lets you keep executing in maven after starting the tomcat - see https://tomcat.apache.org/maven-plugin-trunk/tomcat7-maven-plugin/run-mojo.html

0 votes
VikasB March 10, 2016

I think mvn tomcat:run will wait for return code in order to pass or fail the build. You can try creating  a .bat and return some code. Even I faced this issue but couldn't work on it.

Fernando Nacpil March 10, 2016

So based in this code, Does this mean it will just execute the mvn tomcat:run in the background and execute next the exit?

mvn tomcat:run
exit /b 0

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events