@stefan-balke, we have started with this, but not elaborated carefully. We have used the Selenium framework for this. Would you have an alternative suggestion for this?

Hi @wergo,

for testing interaction and GUI elements, Selenium is one way to do it.
My suggestion aims more at the fundamental level which is easier to test, e.g., load an MXML file and make sure the MEI is what you expect, or save parameters and get what you expected it to save...or set or delete, not necessarily through user interaction. Could also be a call in a script you wrote.

Hi @stefan-balke thank you for your suggestion regarding testing. We have now implemented comprehensive end-to-end tests using PlayWright. Currently, there are 44 individual tests covereing different aspects of the application relating to editing, input, page load, facsimile display and editing, MIDI playback, application settings, UI translation, and URL parameters. These cover the major functionalities of mei-friend.

We will continue developing further tests to cover edge cases and new features as they come along. We are also still working making the existing tests more robust, as some of them can currently exhibit flaky behavior (run well on one occasion, but not on another).

Independently of these end-to-end tests, mei-friend also is able to run internal tests when deployed in the development environment. Currently we use this to validate the completeness of the language packs.

Hi @wergo,

as far as I understand it, playwrights tests on the JS components. How about the Python side of things? Is there anything that should be tested regularly? There should be some endpoints which take only certain types (or should take) etc.

Best,
Stefan