State of tests

What is this?

Eden tests are flaky and that makes it easy for regress issues like this to slip. We need to make eden tests pass at each run, so that no regress issues will pass through.

How we can do it?

Currently, there are 6 test suites running within eden tests, it helps to look through each of them individually, as it narrows down specter of problems that one should look at. Below you can find table which shows state of each test suite and has a link to respective issue for test suite.

How to read the table?

Each test suite has following properties:

• Should Pass indicates if running test suite locally should be successful. If this test suite is failing during GitHub actions, but succeeds when one re-run it, that means it Passes but not Stable
• Stable means that no matter how many times you run test locally or in GitHub actions it will pass
• Issue Link will bring you to respective test suite, which serves as tracker for all failed jobs and discussions how to fix it.

Suite name	Should Pass?	Stable?	Issue Link
Smoke Tests	➕	➖	956
Networking Tests	➕	➖	950
Storage Tests	➖	➖	951
LPC LOC Tests	➖	➖	953
EVE Upgrade Tests	➖	➖	955
User Apps Tests	➕	➖	944

How can I contribute?

• If you see failed test in EVE PR add it to respective Issue
• If you have knowledge of certain area of test suite -- run it locally (every issue has eden commands on how to do it) and try to make it work
• If test is Passing locally, looking through logs of GitHub Action workflows might give us insight on why specific suite is failing on runners
• Any other contributions helping us make eden stable are also welcome :)