Fixing random failures in QA Framework E2E tests

[jayasanka (Jayasanka Weerasinghe)]

@kdaud

All Chrome Tests badge is tracking the ci latest build status for qaframework module. On our ci, these automated tests are run on chrome engine using qa-refapp server that contains the latest changes of RefApp.

@piumal1999 do you think you can investigate why the badge is failing to retrieve the ci build status?

The bamboo workflow (CONTRIB-QA) has been disabled due to poor performance (check this slack thread). It would be better if we could eliminate the CONTRIB-QA plan and integrate the 2.x E2E tests into the 2.x platform and refapp plans.

Update on 2.x E2E tests

Thanks for the update @raff ! It appears that the 2.x related plans are not including any tests. Reference Application - Distribution 2.x: Plan summary - OpenMRS Bamboo Reference Application - Refapp 2.12.0-dev: Plan summary - OpenMRS Bamboo How can we resolve this? Also, have discovered the plan CONTRIB-QA, where 2.x E2E tests were configured. It seems it is triggered when there’s a commit to the GitHub - openmrs/openmrs-contrib-qaframework repo. As far as I know, the job is disabled due …