Closed wridgeu closed 10 months ago
Interesting that it still fails ... but it looks to me like the start of the app takes a bit longer and the testing begins too soon? 🤔 Locally it simply works using npm run start:test
and after everything has started npm run test
.
For fixing the wdi5 tests on #314 I bumped the UI5, wdi5, UI5 tooling and a few other versions. Some version conflict with newest wdio & wdi5 or prettier with pretty-quick were also resolved (no mindless full bump).
I did not bump any action and therefore no node or action versions though. Two tests which relied on virtual list items (clones) were made more resilient by ignoring the clone id at the end. These sporadically failed for me.
Locally it all passed, several times
Disclaimer
I did not comb through the entire codebase to clean up or "migrate" types or anything but it still seemed to work just fine. ^^
Hope it helps a bit.