summaryrefslogtreecommitdiffstats
path: root/features/unsafe_browser.feature
blob: 0701d66963d29b135d73b0fa18e2153459b43d84 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
@product
Feature: Browsing the web using the Unsafe Browser
  As a Tails user
  when I browse the web using the Unsafe Browser
  I should have direct access to the web

  #11458
  @fragile
  Scenario: The Unsafe Browser can access the LAN
    Given I have started Tails from DVD and logged in and the network is connected
    And a web server is running on the LAN
    When I successfully start the Unsafe Browser
    And I open a page on the LAN web server in the Unsafe Browser
    Then I see "UnsafeBrowserHelloLANWebServer.png" after at most 20 seconds

  #11458
  @fragile
  Scenario: Starting the Unsafe Browser works as it should.
    Given I have started Tails from DVD and logged in and the network is connected
    When I successfully start the Unsafe Browser
    Then the Unsafe Browser runs as the expected user
    And the Unsafe Browser has a red theme
    And the Unsafe Browser shows a warning as its start page
    And the Unsafe Browser has no plugins installed
    And the Unsafe Browser has no add-ons installed
    And the Unsafe Browser has only Firefox's default bookmarks configured
    And the Unsafe Browser has no proxy configured
    And the Unsafe Browser uses all expected TBB shared libraries

  #11457, #11458
  @fragile
  Scenario: Closing the Unsafe Browser shows a stop notification and properly tears down the chroot.
    Given I have started Tails from DVD and logged in and the network is connected
    When I successfully start the Unsafe Browser
    And I close the Unsafe Browser
    Then I see the Unsafe Browser stop notification
    And the Unsafe Browser chroot is torn down

  #11458
  @fragile
  Scenario: Starting a second instance of the Unsafe Browser results in an error message being shown.
    Given I have started Tails from DVD and logged in and the network is connected
    When I successfully start the Unsafe Browser
    # Wait for whatever facility the GNOME Activities Overview uses to
    # learn about which applications are running to "settle". Without
    # this sleep, it is confused and it's impossible to start a new
    # instance (it will just switch to the one we already started).
    And I wait 10 seconds
    And I start the Unsafe Browser
    Then I see a warning about another instance already running

  #11458
  @fragile
  Scenario: The Unsafe Browser cannot be configured to use Tor and other local proxies.
    Given I have started Tails from DVD and logged in and the network is connected
    When I successfully start the Unsafe Browser
    Then I cannot configure the Unsafe Browser to use any local proxies

  #11458
  @fragile
  Scenario: The Unsafe Browser will not make any connections to the Internet which are not user initiated
    Given I have started Tails from DVD and logged in and the network is connected
    And I capture all network traffic
    And Tor is ready
    And I configure the Unsafe Browser to check for updates more frequently
    But checking for updates is disabled in the Unsafe Browser's configuration
    When I successfully start the Unsafe Browser
    Then the Unsafe Browser has started
    And I wait 120 seconds
    And the clearnet user has not sent packets out to the Internet
    And all Internet traffic has only flowed through Tor

  Scenario: Starting the Unsafe Browser without a network connection results in a complaint about no DNS server being configured
    Given I have started Tails from DVD without network and logged in
    When I start the Unsafe Browser
    Then the Unsafe Browser complains that no DNS server is configured