TC-NAV-010 — Task completion state persists after app restartappium-android

Persistence · src/tests/tasks/task-nav.spec.ts

0.02

Times are UTC.

Last 16 executions
pass · 98710a6fail · 98710a6fail · 98710a6fail · 98710a6fail · 98710a6pass · 98710a6pass · df59ee1pass · 3b7095fpass · 3b7095fpass · 3b7095fpass · dbafd26pass · ef117f9pass · ef117f9pass · 0621b33pass · 4f26d53pass · 4f26d53
oldest → newest
Why this score
  • MASS_FAILURES_SET_ASIDE4 failure(s) not counted, because most of the suite failed in the same run
Parameterized variants
2 variants · 86% pass across 29 executions

This test runs once per parameter set. Each variant keeps its own identity and score, so one bad input never drags the others down — the roll-up below shows which one is actually failing.

ParametersScoreExecutionsFailedFlaky
appium-android0.021640
appium-ios0.021300
Root cause analysis
App did not reach Login or Home on launch

No analysis to show in this read-only view. AI root-cause analysis needs a model key, so it only runs on an instance that has one.

Related failuressame error cluster · 8 occurrences

1 other test failed with the same error in this run — likely one root cause.

Executions
StatusAttemptCommitBranchDurationWhen
pass#14f26d53main44.5sNov 18, 11:24
pass#14f26d53main43.8sNov 17, 11:48
pass#10621b33main43.2sNov 16, 10:56
pass#1ef117f9main48.0sNov 15, 10:45
pass#1ef117f9main51.6sNov 14, 10:13
pass#1dbafd26main42.2sNov 13, 10:49
pass#13b7095fmain47.9sNov 12, 11:02
pass#13b7095fmain43.9sNov 11, 10:37
pass#13b7095fmain46.5sNov 10, 11:08
pass#1df59ee1main41.3sNov 9, 11:12
pass#198710a6main42.6sNov 7, 09:56
fail#498710a6main21.3sNov 6, 10:44Inspect
fail#398710a6main21.4sNov 6, 10:44Inspect
fail#298710a6main21.6sNov 6, 10:35Inspect
fail#198710a6main21.4sNov 6, 10:35Inspect
pass#198710a6main48.0sNov 5, 10:43