Test DOM output directly

[j-f1]

It would be cool to use something like @testing-library/dom to directly test the rendered output and do things like click buttons, fill out inputs, etc. Since the tool uses the accessibility properties in the DOM API, it would also help make sure the output is accessible.

[MaxDesiatov]

This is spot on! I think as soon as #204 is merged we can start using SnapshotTesting and compare HTML/CSS output with stored expected snapshots of those. In the future we could even make visual snapshots in different browsers with integration tests to ensure wider compatibility.

One other thing I was thinking about is Cypress, which may be a bit easier to maintain than WebDriver end-to-end tests, but I don't have enough experience with either to suggest anything concrete unfortunately.