Running UI tests on Travis-CI with Saucelabs

Thanks @raff for the pointer. Do have any idea why am not able to manually reproduce that failure at int-refapp.openmrs.org?

It seems that modules do not start in the distro docker container. I’ve tried running the docker container locally, but it worked.

@gutkowski, @adamg do you have any clues? Didn’t we find a way to display tomcat logs after timeout?

@raff we did find way to display tomcat logs if tests fail, and configured Travis CI to not stop build if there is no output, but Travis CI automatically stops worker after 50 minutes no matter what we do, see https://docs.travis-ci.com/user/customizing-the-build/#Build-Timeouts

We are failing tests if server responds with 500 for login page, maybe we should do the same for response status 404? That would cut down build time and maybe allow us to see tomcat logs.

We should be failing tests right away for any error (4xx and 5xx) http codes… Could you please adjust that behavior so we can see why test servers are not started properly?

Sure, PR at: https://github.com/openmrs/openmrs-contrib-uitestframework/pull/30

1 Like

Since yesterday, https://ci.openmrs.org/browse/REFAPP-DUT/latest has been failing. Is any of @adamg, @gutkowski, or @raff looking into it? :slight_smile:

Thanks, fixed.