Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 1,006
    • Issues 1,006
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #9897
Closed
Open
Issue created Aug 05, 2015 by intrigeri@intrigeriMaintainer

"The Unsafe Browser can be used in all languages supported in Tails" scenario does not fail when switching locales fail

Originally created by @intrigeri on #9897 (Redmine)

I’ve seen that setting the fa_FA locale fails (which is not surprising, Farsi is not a region AFAIK, and there’s no such locale in Debian) during this test, but this doesn’t trigger a test failure, and the Unsafe Browser is started anyway (not sure with which locale). IMO we should make such a failure fatal, otherwise I suspect we’re actually not testing Unsafe Browser in the languages that we (fail to) set a locale for.

Feature Branch: test/9897-unsafe-browser-langs

Attachments

  • locale-set-fails.png
Edited May 21, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking