Testing the front-end on Github Actions with Selenium
Automatic front-end testing with Selenium on Github Actions is disabled now, due to:
- Problems with properly ending both threads (the test thread, and the coms_server_flask thread which runs the app) in multi-threading in the Github Actions environment;
- Clickable elements being obscured, again only in the Github Actions environment, probably due to different browser windows sizes.
- The macOS environment not having Firefox installed for Selenium webdriver to use for front-end testing.
Proposed Solution
Set up proper testing mechanism once new GUI development commences.
Additional context
Selenium testing has been successfully run with GUI_utest.py on local Windows 10 and MacOS systems. In addition, Github Actions has been set up to run all backend utests on both Windows and MacOS automatically following each push to the Master branch.
Testing the front-end on Github Actions with Selenium
Automatic front-end testing with Selenium on Github Actions is disabled now, due to:
Proposed Solution
Set up proper testing mechanism once new GUI development commences.
Additional context
Selenium testing has been successfully run with
GUI_utest.pyon local Windows 10 and MacOS systems. In addition, Github Actions has been set up to run all backend utests on both Windows and MacOS automatically following each push to the Master branch.