Bug #8714

Step 'Tor is ready' fails randomly

Added by anonym 2015-01-16 17:57:13 . Updated 2015-02-24 22:43:45 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Tails_1.3
Start date:
2015-01-16
Due date:
% Done:

100%

Feature Branch:
bugfix/8714-tor-is-ready-robustness
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

… either because:
1. (Wheezy’s) GNOME3’s hard coded notification timeout of 5 seconds isn’t enough for Sikuli to detect the image, or
2. some bug prevents the notification to be shown, e.g. something like Bug #8685.

IMHO we should drop the part where we look for the notification from this step, but put it in a separate “I see the ‘Tor is ready’ notification” step and test it in a separate scenario.

Subtasks

History

#1 Updated by Tails 2015-01-16 19:15:37

  • Status changed from Confirmed to In Progress

Applied in changeset commit:c42ece64c899a0494d09b6e523046c9cc61920aa.

#2 Updated by anonym 2015-01-16 19:17:35

  • Assignee set to kytv
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

#3 Updated by anonym 2015-01-16 19:19:53

  • Tracker changed from Feature to Bug
  • Feature Branch set to bugfix/8714-tor-is-ready-robustness

#4 Updated by anonym 2015-01-16 19:20:26

  • blocks #8538 added

#5 Updated by kytv 2015-01-19 09:08:12

  • Assignee deleted (kytv)
  • % Done changed from 50 to 90
  • QA Check changed from Ready for QA to Pass

The changes look good. I’ve been using this for a few days and from my perspective it’s an improvement.

Would merge. :)

#6 Updated by intrigeri 2015-01-19 10:37:00

  • Assignee set to intrigeri

#7 Updated by intrigeri 2015-01-19 11:23:24

  • Status changed from In Progress to Fix committed
  • Assignee deleted (intrigeri)
  • % Done changed from 90 to 100

#8 Updated by BitingBird 2015-02-24 22:43:45

  • Status changed from Fix committed to Resolved