Run UI Automation Testing

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

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.

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

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Tuesday in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

158 views 3 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you