test: fix random failing e2e tests#2127
Conversation
cstns
left a comment
There was a problem hiding this comment.
It's a very good attempt, i had a feeling it would do the trick because that was my line of thinking on why tests fail. Unfortunately on subsequent test runs the tests keep failing.
i ran them three times locally. The first pass was successful, the second time the config-nodes/base.spec.js test failed and the third more failed:
|
@cstns I've 404 on https://github.com/user-attachments/files/28065011/tests.log . Could you re-upload, please? |
After a couple more attempts to download it, I finally have it 😕 |
|
@cstns the E2E tests pipeline completed successfully 10 times in a row. I think it is safe to review again. |
|
@cstns I've made some adjustments to run tests reliably on a local environment without breaking the CI pipeline. I've managed to run tests locally without issues 5 times in a row and 10 more times in the CI pipeline. |
|
the |
…nintended cross-widget selector matches during e2e tests.
cstns
left a comment
There was a problem hiding this comment.
Thank you for this!
I also pushed a small fix for the form spec test which was constantly failing locally
|
why are the e2e tests not running against this PR after my latest push? |
I've pushed an irrelevant change to force them to run again. |
|
ok, that's strange. I now see what actions ran but previously I didn't.. I'll blame it on GH's bad day |
Description
This pull request attempts to stabilise failing E2E tests.
Note: Changes introduced in this pull request were created with strong AI support. Caution is required during the review.
Related Issue(s)
Checklist
flowforge.yml?FlowFuse/helmto update ConfigMap TemplateFlowFuse/CloudProjectto update values for Staging/ProductionLabels
area:migrationlabel