I’d like to see if I can figure out why the UI tests are flaky. I found this conversation and others:
One thing I do not understand: Looking at Bamboo build log, it appears that the UI tests are actually being run on SauceLabs, but I don’t see where that is actually hooked up. How is that done? I looked at the Bamboo plugins, but I don’t see SL there. Can I run the UI tests on SauceLabs myself? Is there a SauceLabs OpenMRS-Testing account? Or it looks like the tests are just being run under Rafa’s account? Please advise.
Ignoring SauceLabs for now, running tests locally…
I observe that all the recent UI test failures on bamboo are actually this:
javax.ws.rs.BadRequestException: HTTP 400 Bad Request
which has nothing to do with the actual Selenium UI tests, but rather is coming from the REST call the tests make during setup to create test Persons and such. I was able to reproduce this after repeated trials and I’m pretty sure the problem is in the birthdate field - the test was using 0-11 for the month instead of 1-12. When I fixed that locally, I could not get the error to happen. So that’s one fix I definitely think should go in. It’s actually in the uitestframework.
I also found we’re using a rather out of date version of Selenium, so I’d like to update that too. Also the chromedrivers. Oh, and I found a missing dependency on commons-io that only shows up when you use chrome.
I know I used to have commit privileges for uitestframework and ui-tests in refapp, but perhaps I should do a pull request for now because it’s been so long - get Rafa or someone to code-review.
In Reply To
leebreisacher https://talk.openmrs.org/users/leebreisacher Tester
Ignoring SauceLabs for now, running tests locally… I observe that all the
recent UI test failures on bamboo are actually this:
javax.ws.rs.BadRequestException: HTTP 400 Bad Request which has nothing to
do with the actual Selenium UI tests, but rather is coming from the REST
call the tests mak…
Many modules are set up to be released from bamboo. These automatically
update the refapp distro’s pom.xml with their released version.
uitestframework is not released from bamboo, so I manually updated the
In Reply To
darius https://talk.openmrs.org/users/darius Darius Jazayeri
You’re correct. Current changes to uitf are building the 1.8-snapshot
version, but the distro pom declares that the distribution will use an
earlier version. You should change the distro pom to depend on the latest
version of uitf (1.8-SNAPSHOT), so the distro build can see your latest