Is your feature request related to a problem? Please describe.
Occasionally we have regression bugs such as #960 which are not related to a recent change in an obvious way, so it is difficult to know which parts of the user interface to manually test before a release in order to catch these bugs.
Describe the solution you'd like
Some kind of automated browser testing included in the Continuous Integration so we can write a test for each regression we find, so once we catch it once it can never happen again.
Additional context
This feature request does not require an extensive suite of tests. This issue is being raised just to get the automation working and a few well documented example tests so it is then easy for others to add tests in future as required.
Is your feature request related to a problem? Please describe. Occasionally we have regression bugs such as #960 which are not related to a recent change in an obvious way, so it is difficult to know which parts of the user interface to manually test before a release in order to catch these bugs.
Describe the solution you'd like Some kind of automated browser testing included in the Continuous Integration so we can write a test for each regression we find, so once we catch it once it can never happen again.
Describe alternatives you've considered There is some discussion on Discord about the possibility of using Selenium with a webdriver for either Firefox or Chrome.
Additional context This feature request does not require an extensive suite of tests. This issue is being raised just to get the automation working and a few well documented example tests so it is then easy for others to add tests in future as required.