Project

General

Profile

Bug #12683

Move DAVE manual test suite out of the Tails release process

Added by intrigeri 4 months ago. Updated about 1 month ago.

Status:
Confirmed
Priority:
Elevated
Assignee:
Category:
Installation
Target version:
Start date:
06/12/2017
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Contributors documentation
Blueprint:
Easy:
Affected tool:
Download and Verification Extension

Description

In #11799 we've added DAVE tests to https://tails.boum.org/contribute/release_process/test/. That's a great start! But, there's a but:

  • Most of these tests are orthogonal to the Tails release process, so it's suboptimal to have on the critical path to a Tails release. The fact that some of these tests seem too unclear, at least for a few of us, doesn't help (#12005).
  • The goal of #11799 was "to detect problems with new Firefox versions early enough", but the testing instructions merely require "a Firefox-based browser"; so if the tests are performed in the ISO under testing, i.e. with an oldish Firefox ESR, then this testing process is not addressing the initial goal; and if the tests are performed elsewhere, with a recent Firefox, then we're not verifying that DAVE works well in the upcoming version of Tails, although that would be a useful additional goal of running these tests during the Tails release process.

So I propose:

  1. Keep the simplest test in the Tails manual test suite: download, pause/resume, appears in the downloads list.
  2. Move all other tests to a dedicated DAVE test suite, that shall be run (probably by the DAVE maintainer, but suggestions are welcome):
    1. at DAVE release time;
    2. whenever a new Firefox is released.
  3. Consider automating these tests before we get bored and sloppy and start secretly skipping the "whenever a new Firefox is released" tests ;)

But I might have missed some reasons why things currently are done like this, so please correct my assumptions/reasoning if needed :)


Related issues

Related to Tails - Bug #12005: Problems with DAVE manual tests In Progress 11/30/2016

History

#1 Updated by intrigeri 4 months ago

  • Related to Bug #12005: Problems with DAVE manual tests added

#2 Updated by intrigeri about 1 month ago

  • Priority changed from Normal to Elevated
  • Target version changed from Tails_3.2 to Tails_3.3

I suggest you ignore DAVE until the 3.2 release and then put it on your list of top priorities for the 3.3 cycle.

Also available in: Atom PDF