Bug #17684

Test suite failures: 4.6 vs. features/torified_browsing.feature

Added by CyrilBrulebois 2020-05-05 21:58:03 . Updated 2020-05-07 09:02:19 .

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Here are the results for the 4.6 test run, from https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/2325/console (the previous job was aborted…):

Failing Scenarios:
cucumber features/additional_software_packages.feature:46 # Scenario: My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
cucumber features/additional_software_packages.feature:69 # Scenario: Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
cucumber features/additional_software_packages.feature:114 # Scenario: I am notified when Additional Software fails to install a package
cucumber features/po.feature:7 # Scenario: check all PO files
cucumber features/torified_browsing.feature:7 # Scenario: The Tor Browser cannot access the LAN

Comments:

  • All of ASP (features/additional_software_packages.feature) passed locally, as is usual: something is wrong in Jenkins and we have regular failures.
  • Problems with PO files were known in advance, and will be the topic for another bug report.
  • features/torified_browsing.feature gave the following results locally (running on a stretch system).
Failing Scenarios:
cucumber features/torified_browsing.feature:46 # Scenario: Watching a WebM video
cucumber features/torified_browsing.feature:96 # Scenario: The Tor Browser's "New identity" feature works as expected
cucumber features/torified_browsing.feature:106 # Scenario: The Tor Browser should not have any plugins enabled

17 scenarios (3 failed, 14 passed)
180 steps (3 failed, 7 skipped, 170 passed)
89m37.909s

All 3 failures were due to:

    And the Tor Browser loads the startup page                                     # features/step_definitions/common_steps.rb:422
      try_for() timeout expired (Timeout::Error)
      ./features/support/helpers/misc_helpers.rb:111:in `rescue in try_for'
      ./features/support/helpers/misc_helpers.rb:36:in `try_for'
      ./features/step_definitions/browser.rb:127:in `page_has_loaded_in_the_Tor_Browser'
      ./features/step_definitions/common_steps.rb:433:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails roadmap)$/'
      features/torified_browsing.feature:109:in `And the Tor Browser loads the startup page'

All three screenshots show the exact same image, except for the clock that differs a little. See attachment for one of them.

The case we’re trying to address is the startup page one in:

Given /^the Tor Browser loads the (startup page|Tails homepage|Tails roadmap)$/ do |page|
  case page
  when "startup page"
    titles = ['Tails', 'Tails - Trying a testing version of Tails']
  when "Tails homepage"
    titles = ['Tails - Privacy for anyone anywhere']
  when "Tails roadmap"
    titles = ['Roadmap - Tails - Tails Ticket Tracker']
  else
    raise "Unsupported page: #{page}"
  end
  page_has_loaded_in_the_Tor_Browser(titles, $language)
end

and as one can see on the screenshot, the page’s title is “Tails - Welcome to Tails!”

Please help get that fixed before the next release, such test failures can trigger huge delays plus thinking/guessing what to do.


Files


Subtasks


Related issues

Is duplicate of Tails - Bug #17007: JavaScript sometimes blocked on Tor Browser first start ⇒ "Watching a WebM video over HTTPS" and "Playing an Ogg audio track" scenarios are fragile: blocked by NoScript click-to-play Confirmed
Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by CyrilBrulebois 2020-05-05 21:58:17

#2 Updated by intrigeri 2020-05-07 09:00:51

  • is duplicate of Bug #17007: JavaScript sometimes blocked on Tor Browser first start ⇒ "Watching a WebM video over HTTPS" and "Playing an Ogg audio track" scenarios are fragile: blocked by NoScript click-to-play added

#3 Updated by intrigeri 2020-05-07 09:02:19

  • Status changed from Confirmed to Duplicate

> and as one can see on the screenshot, the page’s title is “Tails - Welcome to Tails!”

That’s a symptom of Bug #17007: home.js is responsible for changing the page’s title to “Tails”, and apparently that never happened here, which is consistent with Bug #17007.