RATEST-349: Run 2.x E2E tests on chrome and firefox via github actions

[anjula-sack]

Requirements

• This PR has a title that briefly describes the work done, including the ticket number if there is a ticket.
• I have tested the changes locally and verified that they work as intended.
• I have added comments to my code where necessary to help others understand my changes.
• I have read and agree to the Contributing Guidelines of this project.

Summary

For a while RefApp 2.x e2e tests have been running on the Firefox browser in GitHub actions. In this PR the all the tests are being updated to run on chrome as well. This was achieved by updating the github actions workflows.

Screenshots

None.

Related Issue

https://issues.openmrs.org/browse/RATEST-349

Other

None.

[kdaud]

Thanks @anjula-sack for pulling this up. Could you help me understand how this work?

[anjula-sack]

Thanks @anjula-sack for pulling this up. Could you help me understand how this work?

The strategy section defines a matrix strategy that allows the job to run multiple times with different configurations. In this case, the matrix specifies a variable browser with two possible values: firefox and chrome. This means that the job will run twice, once with browser set to firefox and once with browser set to chrome.

[kdaud]

The strategy looks great!

Does this configuration overrides the global setting here?

[anjula-sack]

The strategy looks great!

Does this configuration overrides the global setting here?

No, It just downloads the chrome selenuim driver and runs the tests. Basically everything is same as before we just have extra jobs to run tests on chrome

[kdaud]

So which browser is being used by the tests as per this commit?

[anjula-sack]

So which browser is being used by the tests as per this commit?

Both of them. Check the tests, you can see every test has been ran twice. One with chrome and the other with firefox.

[kdaud]

Have skimmed through the logs and noticed all the two jobs are running on firefox browser.

https://github.com/openmrs/openmrs-contrib-qaframework/actions/runs/5076943535/jobs/9119634346?pr=485#step:7:11615

https://github.com/openmrs/openmrs-contrib-qaframework/actions/runs/5076943535/jobs/9119634430?pr=485#step:7:11636

Could you take a look at the logs to find out why this is happening so? What would happen when you switch browser order and begin with chrome?.

strategy:
      matrix:
        browser:
          - chrome
          - -firefox`

[Piumal1999]

Good job @anjula-sack . I added some comments

[anjula-sack]

@kdaud Check now. It's running on both now. I had to update the properties.

[kdaud]

Great work!
Thanks @anjula-sack

[kdaud]

@anjula-sack, revert the changes that were made in the platform ui tests.

[anjula-sack]

@anjula-sack, revert the changes that were made in the platform ui tests.

Didn't get you?

[kdaud]

The platform ui tests should be excluded from the changes and that's why they're failing plans in master, look out for the .yaml files starting with platform-..yaml and revert their respective changes.