Topics to discuss:

• Anton:
  • https://github.com/status-im/status-go/issues/6064 coverage priorities
  • Waku fleet for every test run, similar to what we do with anvil
    • nightly (or any other schedule for prod/staging fleets)
  • geth.log from every container for every run
  • Test Statistics
• @Igor Sirotin
  • PR-level linter check
  • https://github.com/status-im/status-go/issues/6144
  • https://github.com/status-im/status-go/issues/6191
• Florin:
  • separate reliability tests into separate suite and job (ideally with github actions)
  • codecov/patch taking so long or stuck
  • Waku FURPS requirements
• Some time ago we were discussing on this https://github.com/status-im/status-go/issues/5738

To Do:

Anton:

add env vars for restore and create account

add geth.log from every container

add a thingy to check that the log has no leaks

Florin:

CLI tests (reliability) are going to move to /test-functional in status-go repo, this tests are going to run in separate GithubAction job

add linter and make black

@Igor Sirotin

Provide a way to set custom Waku fleet and storenodes to status-go.