Menu

The device test was there. CI never ran it.
πŸ“°

The device test was there. CI never ran it.

DEV Community: mobileΒ·John AdibΒ·14 days ago
#pAc63i8v
#devtomobile#devto#dev#flow#suite
Reading 0:00
15s threshold

By October, our Maestro end-to-end testing setup for the mobile app looked well covered. Every one of the 99 routes expected to have automated device coverage had a flow in the repository. Then we traced what ran in CI.

Only 28 routes were reached by flows that CI executed. The other 71 depended on quarantined flows. That gap mattered more than the repository inventory: our release decisions needed evidence from tests that actually ran on mobile devices.

As the engineering manager, I needed to know why the existing flows weren't producing evidence before asking the team to write more.

Follow the call graph

Our Maestro end-to-end tests were assembled in layers. A leaf flow covered a product journey. Shared subflows handled repeated steps. Suite aggregates assembled journeys for a run. The cloud jobs called those aggregates.

That last connection mattered. A new leaf could be well written, reviewed, and tagged, yet never execute if no aggregate called it. A tag on the leaf did not put it into a cloud job.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.