You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the specific case of what you've posted it might have to do with #1073.
But the real issue here has already existed 11 years ago when @wvengen has put a workaround in place: 8ac7cbf
<- That is why - while the test you mentioned failed the first time - the pipeline still succeeded as it passed the second time.
(rspec-rerun tries the test one more time by default).
While wvengen was right back then (integration tests indeed can be brittle) - I think we should try and eventually remove his workaround (i.e. uninstall rspec-rerun) to make things more reproducible for developers.
This can however be arduous as the current integration tests are hard to debug! So I wonder if we shouldn't postpone this task until we have agreed upon a strategy for a frontend makeover - also see my comment here: #1140 (comment) (The part about a e2e/integration tests for a PWA)
Yes. This need some discussion. Integration tests should not be brittle as that more or less means they are not effectively proving what you want to have verified.
BTW: for me integration means checking how parts of the puzzle interact (which may need some mocking here or there) and E2E
5A97
the full interaction as a user or endpoint would use the system.
It's a bit confusing to me that sometimes (every second time?), the test still fails, but the checks pass, like they did in #1082 after I amended my commit the last time.
https://github.com/foodcoops/foodsoft/actions/runs/14096355453/job/39484356726?pr=1082#step:9:325
but also in #1143:
https://github.com/foodcoops/foodsoft/actions/runs/14007877933/job/39224023648?pr=1143#step:9:325
The text was updated successfully, but these errors were encountered: