Skip to content

Improve client testing #17713

@nijel

Description

@nijel

Describe the problem

Currently issues like #17711 go unnoticed through our CI because there is really no testing of client code.

Solution brainstorm

There must be a way to test that client code works well. I'd like to have some direct testing of JavaScript code that updating deps didn't break anything, but our code might not be ready for that.

Describe alternatives you have considered

We might look into extending Selenium tests. It might be even possible to fail on JavaScript errors there.

Screenshots

No response

Additional context

No response

Metadata

Metadata

Labels

Waiting for: ImplementationAdded to a milestone, will be resolved according to the milestone timeline.

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions