Bug #10288: Fix newly identified issues to make our test suite more robust and faster
The "the Tor Browser loads the (startup page|Tails roadmap)" step is fragile
Refactoring would allow
retry_tor magic to be used for this step in case loading the page fails.
#3 Updated by anonym almost 4 years ago
- Subject changed from Refactor the "loaded the Tails roadmap" step in the test suite to The "the Tor Browser loads the (startup page|Tails roadmap)" step is fragile
The 'I see the Tails roadmap URL' doesn't use the retrying-magic we have in the 'I open the address ...' step. We should refactor out that code from the latter so it can be used in the former step.
Sorry, I meant that the '
the Tor Browser has started and loaded the Tails roadmap' step is fragile. Hence we need to refactor out the retrying code from the '
I open the address ...' step so it can be used in this step as well.
Note that the problematic step's definition matches
/^the Tor Browser (?:has started and )?load(?:ed|s) the (startup page|Tails roadmap)$/ so all scenarios using it for the startup page case are also fragile. That's another 11 scenarios (essentially all of
#7 Updated by anonym almost 4 years ago
- Assignee changed from anonym to kytv
- Target version changed from Tails_1.7 to Tails_1.8
Could this reasonably be part of the rest of the test suite work you have? Optimistically reassigning to you (note that I'll do this for the other children of #10288, but won't comment there).
In any case, let's postpone this to 1.8. We have way to much on our plates this cycle.