GitLab

ca-certificates 20161130+nmu1+deb9u1 removed the certificate we used
for testing.

The "Getting started" page had a 'Found a bug?' heading but the "Documentation"
page has no such thing.

- /getting_started is very old and needs a serious lifting.

- During the user testing of the Additional Software beta, 3 out of 5
  participants ended up on this page. None of them read it. 2 used it to reach
  /doc which is what they were looking for. 1 got lost and ended up on /design.

I cannot reproduce (in Tails 3.6.2) the Tor Browser bug that made us disable
this test.

The last use case for this image was removed in
commit:0cf89c9d.

I've seen this test fail locally due to not waiting long enough:
Electrum did start a few seconds after Cucumber reported
it failed to start.

It takes a bit of time and without that waiting, the step fails.

Refs: #15022

If systemd detects that the system clock is before its build date, it
will do the same thing as Tails: setting the system clock to the build
date.

So, after Tails' init, the system time will be set to:

    max(system time (RTC), Tails build date, systemd build date)

I saw it take 11 seconds on my system.

Not sure if relevant, but since this is the only time this has ever
happened on my system (which wasn't under load, BTW) I'll mention it:
this happened while testing feature/8243-meek and it's upgraded
systemd (from 232-25+deb9u1 to 237-3~bpo9+1).

Upgrading to 3.x requires non-trivial modifications, so I took
the (slight) extra time to make us less dependent on future
changes (and possibly solving robustness issues for free).

Refs: #15022, #10475, #11697

Refs: #8775

Using chutney requires to use non-onion APT sources.

Refs: #14572, #11556

Refs: #15336

This image was invalidated during our Donation campaign was running,
and then by a Tor Browser bug (#14962). Bumping images is boring so
let's rely on Dogtail instead.

To make this scenario more robust we also switch to something else
than the start page, and restart the browser between save/open in
order to prevent Dogtail e.g. finding the old page that we just saved
instead of the saved version we just opened.

Refs: #14935, #14962

This reverts commit 15ff2632.

https://labs.riseup.net/code/issues/15024#note-6 was missed
when we closed #15024.

Refs: #15332

Test suite: mark scenarios that use the "The Report an Error launcher will…" step as fragile (refs: #15321)

Instead of Python, whose glob implementation lacks curly brace
expansion.

The "non-onion sources" part of this step is achieved through the 'I
configure APT to use non-onion sources' step.