End to end and smoke tests give a really valuable angle on what the app is doing and can warn you about failures before they happen. However, because they’re working with a live app and a live database over a live network, they can introduce a lot of flakiness. Beyond just changes to the app, different data in the environment or other issues can cause a smoke test failure.

How do you handle the inherent flakiness of testing against a live app?

When do you run smokes? On every phoenix branch? Pre-prod? Prod only?

Who fixes the issues that the smokes find?

  • learningduck
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Reading the 3rd paragraph and I see myself 😄. Glad that you and the team managed to add another layer of testing successfully.