Project

General

Profile

Feature #8539

Make the test suite robust enough to be run as part of a CI setup

Added by intrigeri over 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Test suite
Target version:
Start date:
10/05/2014
Due date:
03/06/2015
% Done:

100%

QA Check:
Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Subtasks

Bug #6092: Tails Installer sometimes hangs late in the installation processResolved

Bug #9715: Retry wget in the test suite when failing to resolve a hostResolved

Bug #9633: waitAny is failing to find images that are on the screenResolved

Bug #10116: "Watching a WebM video" test is fragileResolved

Bug #10219: Escape regexp used to match nick in CTCP repliesResolved


Related issues

Blocks Tails - Feature #5288: Run the test suite automatically on autobuilt ISOs Resolved 01/03/2014 10/15/2015

History

#2 Updated by intrigeri over 4 years ago

  • Blocks Feature #5288: Run the test suite automatically on autobuilt ISOs added

#3 Updated by anonym over 4 years ago

  • Target version changed from Hardening_M1 to Tails_1.5

#4 Updated by anonym over 4 years ago

  • Target version changed from Tails_1.5 to Tails_1.4

#5 Updated by anonym about 4 years ago

  • Assignee set to anonym

#6 Updated by kytv about 4 years ago

  • Related to Bug #8686: Sometimes notification-daemon aborts, causing desktop notifications to not be displayed added

#7 Updated by kytv about 4 years ago

  • Related to deleted (Bug #8686: Sometimes notification-daemon aborts, causing desktop notifications to not be displayed)

#8 Updated by intrigeri about 4 years ago

  • Target version changed from Tails_1.4 to Tails_1.4.1

Postponing. IIRC we didn't really expect to complete all of the sub-tasks during this cycle, right?

Also, it's become the fallback parent ticket for all kinds of test suite robustness bugs. I think we'll need to find a better tool at some point to track this class of problems, but I think we can go on like that for a couple more cycles.

#9 Updated by anonym almost 4 years ago

  • Blocked by Feature #9515: Improve test suite robustness vs transient network errors added

#10 Updated by intrigeri almost 4 years ago

  • Blocked by deleted (Feature #9515: Improve test suite robustness vs transient network errors)

#11 Updated by intrigeri almost 4 years ago

  • Target version changed from Tails_1.4.1 to Tails_1.5

Postponing again.

#12 Updated by intrigeri almost 4 years ago

  • Status changed from Confirmed to In Progress

#13 Updated by intrigeri almost 4 years ago

  • Target version changed from Tails_1.5 to Tails_1.6

(The only remaining subtask is scheduled for 1.6.)

#14 Updated by intrigeri over 3 years ago

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)

intrigeri wrote:

Also, it's become the fallback parent ticket for all kinds of test suite robustness bugs. I think we'll need to find a better tool at some point to track this class of problems, but I think we can go on like that for a couple more cycles.

I think it's time to kill this ticket. Whatever is too fragile in Jenkins should now be filed with priority = high (at least for a couple cycles IMO), marked as blocking #8668, with an assignee and a sensible target version. If we later realize we need a way to list all such issues, we'll see (I suspect that "Blocks" will be a more appropriate relationship than parenthood).

#15 Updated by bertagaz over 3 years ago

  • Status changed from Fix committed to Resolved

Killing this ticket then. Let's use other means to go on with this.

Also available in: Atom PDF