Feature #10379

Check that we do not see any error pages in the "I open the address" step.

Added by kytv 2015-10-15 06:00:50 . Updated 2018-04-06 13:00:40 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Start date:
2015-10-15
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

anonym wrote:

> In the error screenshot I can see that the Tor Browser is showing the “The connection has timed out” page. Something must be wrong with our recent improvements in the ‘I open the address ...’ step since it accepted this page. Possibly the existing condition isn’t enough, but we should also check that we do not see this particular error page, or perhaps any error page. Thoughts?

I agree that checking for any error page would be good to do.

Subtasks

Related issues

Related to Tails - Bug #10381: The "I open the address" steps are fragile Resolved 2015-10-15
Blocked by Tails - Feature #9521: Use the chutney Tor network simulator in our test suite Resolved 2016-04-15

History

#1 Updated by kytv 2015-10-15 06:01:11

  • Status changed from New to Confirmed
  • Parent task set to Bug #10288

#2 Updated by intrigeri 2015-10-16 02:37:32

  • Assignee set to anonym

kytv, anonym: this has a target version (rightfully I guess), so it needs an assignee. Tentatively assigning to anonym, please sort this out together :)

#3 Updated by intrigeri 2015-10-16 02:37:43

  • blocks #8668 added

#4 Updated by anonym 2015-10-16 05:51:34

  • Assignee changed from anonym to kytv
  • Target version changed from Tails_1.7 to Tails_1.8

#5 Updated by intrigeri 2015-11-06 06:05:48

  • Deliverable for set to 270

#6 Updated by intrigeri 2015-11-06 06:06:41

  • related to Bug #10381: The "I open the address" steps are fragile added

#7 Updated by kytv 2015-11-06 11:56:01

  • Target version changed from Tails_1.8 to 246

#8 Updated by anonym 2015-11-06 12:45:05

  • Assignee changed from kytv to anonym
  • Target version changed from 246 to Tails_1.8

I think this can be solved together with { Bug #10442, Bug #10381, Bug #10376 }.

#9 Updated by intrigeri 2015-12-05 13:20:33

  • Target version changed from Tails_1.8 to Tails_2.0

(We’re going to mark as fragile all tests that depend on Tor to have bootstrapped for the moment => not so urgent.)

#10 Updated by anonym 2016-01-06 14:06:20

  • Target version changed from Tails_2.0 to Tails_2.2

#11 Updated by anonym 2016-02-20 13:21:10

  • Priority changed from Normal to Elevated
  • Target version changed from Tails_2.2 to Tails_2.4

#12 Updated by anonym 2016-02-20 14:56:33

  • Priority changed from Elevated to Normal
  • Target version deleted (Tails_2.4)
  • Deliverable for deleted (270)

I’m gonna gamble and focus on Chutney (Feature #9521) hoping it will fix this issue.

#13 Updated by anonym 2016-02-20 14:57:38

  • blocked by Feature #9521: Use the chutney Tor network simulator in our test suite added

#14 Updated by Anonymous 2018-01-15 11:30:48

Did Chutney fix the issue? If yes, please close this ticket.

#15 Updated by Anonymous 2018-01-15 11:31:00

  • blocked by deleted (#8668)

#16 Updated by Anonymous 2018-01-15 11:31:05

  • related to #8668 added

#17 Updated by Anonymous 2018-01-15 11:31:33

This ticket does not seem to be part of a deliverable, at least it’s not marked as such, so I’m unblocking the parent ticket.

#18 Updated by anonym 2018-04-06 13:00:40

  • Status changed from Confirmed to Rejected
  • Assignee deleted (anonym)

We now have the the Tor Browser shows the "..." error step instead. Sometimes an error is expected, so this ticket is just a bad idea => rejecting.