Bug #17004

Update test suite to cope with Unsafe Browser homepage changes

Added by intrigeri 2019-08-29 16:38:11 . Updated 2019-09-05 00:03:23 .

Status:
Resolved
Priority:
Elevated
Assignee:
hefee
Category:
Test suite
Target version:
Start date:
Due date:
% Done:

100%

Feature Branch:
test/17004-unsafe-browser-homepage-stretch, test/17004-unsafe-browser-homepage-buster
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Unsafe Browser
Deliverable for:

Description

wiki/src/misc/unsafe_browser_warning.html has been changed today on master and devel, in a way that sometimes breaks the test suite.

We need to:

  1. Merge master into stable.
  2. Fork a branch off stable.
  3. On that branch, update features/images/UnsafeBrowserStartPage.*.png.
  4. Ensure this fixes the problem: the “The Unsafe Browser can be used in all languages supported in Tails” scenario should pass without leaving fuzzy Sikuli candidates behind.
  5. Review and merge into stable.
  6. Merge stable into devel.
  7. Update the pictures again on devel: the page is rendered differently on Buster.
  8. Ensure this fixes the problem on devel too: the “The Unsafe Browser can be used in all languages supported in Tails” scenario should pass without leaving fuzzy Sikuli candidates behind.

Subtasks


Related issues

Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by intrigeri 2019-08-29 16:39:10

#2 Updated by intrigeri 2019-08-30 08:34:17

  • Assignee set to intrigeri

#3 Updated by intrigeri 2019-08-30 15:33:05

  • Status changed from Confirmed to In Progress

Applied in changeset commit:tails|cf83fb2beaa531ee1d45a19b5247024a443c7d3b.

#4 Updated by intrigeri 2019-08-30 15:35:45

  • Status changed from In Progress to Needs Validation
  • Assignee deleted (intrigeri)
  • Feature Branch set to test/17004-unsafe-browser-homepage-stretch, test/17004-unsafe-browser-homepage-buster

Please review and merge:

  • test/17004-unsafe-browser-homepage-stretch into stable
  • test/17004-unsafe-browser-homepage-buster into devel

I’ve already merged the former into the latter, to ensure we resolve the merge conflict in favor of the Buster image for devel.

I’ve run the affected scenario locally (The Unsafe Browser can be used in all languages supported in Tails) from each branch, respectively on an ISO built from stable and one built from devel. Passed with flying colors.

#5 Updated by intrigeri 2019-08-30 15:36:25

  • Assignee set to hefee

@hefee, can you handle this one by the end of the week?

#6 Updated by intrigeri 2019-08-30 18:25:25

  • Status changed from Needs Validation to In Progress

Applied in changeset commit:tails|0156e8dc61aca9a0edc4f3cc358ae3e8bd0ac2ec.

#7 Updated by intrigeri 2019-08-30 18:31:18

  • Status changed from In Progress to Needs Validation

Meh.

#8 Updated by Anonymous 2019-08-31 13:08:52

  • Status changed from Needs Validation to Fix committed
  • % Done changed from 0 to 100

Applied in changeset commit:tails|3de25862c16b5df756620e4e21f5cf69dd2b1253.

#9 Updated by CyrilBrulebois 2019-09-05 00:03:23

  • Status changed from Fix committed to Resolved