[Deliverable] Status-cli-tests to simulate mobile environment

[fryorcraken]

Summary

Work with the Vac-QA team and Status Core Mobile team to improve the variety of environments status-cli-tests are run through, and simulate what can happen to an application running on iOS and Android, such as network loss, ipv6, network switch, app in background, app killed due to battery saving, etc.

[fryorcraken]

Meeting on 24 Feb with Status Mobile & QA, Vac-QA, Vac-DST teams.
AI notes: https://docs.google.com/document/d/1Fr776mnutyz68tl9R7jZUW0Xw5iTfLx0yRjtQ7ybbuI/edit?tab=t.ksr5nwm044hz

Next steps

• @fryorcraken to create notion page to track
  • events/environment to test - @ilmotta to help translate mobile events to process/network context (e.g what signal is being sent to a process when X happens)
  • Functional tests
    • First use same tests as in https://status-im.github.io/status-cli-tests/
    • @churik to help prioritize new tests/pain point (e.g. "sync on wifi" option).
• Vac-QA/DST @fbarbu15 @AlbertoSoutullo to agree and plan the work.

[fryorcraken]

A few months ago the phase 1 scenarios to the status-backend reliability tests (for ref) were added.

Hence closing this deliverable as done.

My expectation is that with the new chat stack, the ownership should be clearer and we will then be able to have:

• Vac-QA tests done on status-backend, owned by Status
• New Vac-QA tests done on the new Waku Chat SDK stack (name TBC), where we will produce a test binary that can be run for what the Chat SDK is supposed to do.

We are not planning for this new binary to be done in our first Chat SDK milestone. For now, we will rely on Vac-QA tests and Status QA tests to pass.

Once we plan to reach some feature equivalence and integration, we can plan this new binary and re-work the status-backend ownership.