-
I've been investigating flaky E2E tests, improving the error messages to see more what's going on (see https://github.com/loculus-project/loculus/pull/1881/commits/0f1d4a2a91af1251847e3f0a42acc9936195…
-
### Front-end side
Our application is growing day by day and the manual testing is going to be unmaintainable. For this reason, I think we should add unit tests for the frontend side (all the Angul…
-
Want to contribute for hactoberfest? Help us improve our frontend E2E testing. We use a framework called Cypress and would like to extend the E2E testing to more CRUD based operations in our frontend …
-
### Current behavior
When trying to implement component testing in our monorepo I get the error:
```
TypeError
Your configFile threw an error from: cypress.config.ts
We stopped running your…
-
Create an automated testing for build/setup/E2E that allows testing CLRIE changes.
-
@ddalp built out some visual tree comparison test infrastructure recently: #3754
We're going to use that more as we do new feature work, but we have a lot of test debt in everything we built before …
-
There is a testing extension for Quasar Framework that introduces code-coverage support for Cypress e2e testing: [link](https://github.com/quasarframework/quasar-testing/tree/dev/packages/e2e-cypress)…
-
This is critically important - there is no automated testing. We need unit and/or end-to-end testing examining as many scenarios as possible. (edit: we do have E2E testing now but could still use some…
-
Need to add E2E testing.
-
The Mosaic packages require a more thorough test plan in order to have confidence in the tool.
As part of this issue it would be good to begin the process (ordered by priority)
1. Encourage new Pull…