summaryrefslogtreecommitdiffstats
path: root/features/usb_install.feature
diff options
context:
space:
mode:
Diffstat (limited to 'features/usb_install.feature')
-rw-r--r--features/usb_install.feature210
1 files changed, 65 insertions, 145 deletions
diff --git a/features/usb_install.feature b/features/usb_install.feature
index 780c32a..b40ca93 100644
--- a/features/usb_install.feature
+++ b/features/usb_install.feature
@@ -8,13 +8,7 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
@keep_volumes
Scenario: Installing Tails to a pristine USB drive
Given a computer
- And the computer is set to boot from the Tails DVD
- And the network is unplugged
- And I start the computer
- When the computer boots Tails
- And I log in to a new session
- And GNOME has started
- And all notifications have disappeared
+ And I start Tails from DVD with network unplugged and I login
And I create a new 4 GiB USB drive named "current"
And I plug USB drive "current"
And I "Clone & Install" Tails to USB drive "current"
@@ -23,17 +17,20 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
And I unplug USB drive "current"
@keep_volumes
- Scenario: Booting Tails from a USB drive without a persistent partition and creating one
+ Scenario: Booting Tails from a USB drive in UEFI mode
Given a computer
- And the computer is set to boot from USB drive "current"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
+ And the computer is set to boot in UEFI mode
+ When I start Tails from USB drive "current" with network unplugged and I login
+ Then the boot device has safe access rights
+ And Tails is running from USB drive "current"
And the boot device has safe access rights
- And I log in to a new session
- And GNOME has started
- And all notifications have disappeared
- Then Tails seems to have booted normally
+ And Tails has started in UEFI mode
+
+ @keep_volumes
+ Scenario: Booting Tails from a USB drive without a persistent partition and creating one
+ Given a computer
+ And I start Tails from USB drive "current" with network unplugged and I login
+ Then the boot device has safe access rights
And Tails is running from USB drive "current"
And the boot device has safe access rights
And there is no persistence partition on USB drive "current"
@@ -44,19 +41,14 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
@keep_volumes
Scenario: Booting Tails from a USB drive with a disabled persistent partition
Given a computer
- And the computer is set to boot from USB drive "current"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And I log in to a new session
- Then Tails seems to have booted normally
- And Tails is running from USB drive "current"
+ And I start Tails from USB drive "current" with network unplugged and I login
+ Then Tails is running from USB drive "current"
And the boot device has safe access rights
And persistence is disabled
But a Tails persistence partition with password "asdf" exists on USB drive "current"
@keep_volumes
- Scenario: Writing files to a read/write-enabled persistent partition
+ Scenario: Persistent browser bookmarks
Given a computer
And the computer is set to boot from USB drive "current"
And the network is unplugged
@@ -69,6 +61,28 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
And GNOME has started
And all notifications have disappeared
And persistence is enabled
+ And persistent filesystems have safe access rights
+ And persistence configuration files have safe access rights
+ And persistent directories have safe access rights
+ And I start the Tor Browser in offline mode
+ And the Tor Browser has started in offline mode
+ And I add a bookmark to eff.org in the Tor Browser
+ And I warm reboot the computer
+ And the computer reboots Tails
+ And I enable read-only persistence with password "asdf"
+ And I log in to a new session
+ And GNOME has started
+ And I start the Tor Browser in offline mode
+ And the Tor Browser has started in offline mode
+ Then the Tor Browser has a bookmark to eff.org
+
+ @keep_volumes
+ Scenario: Writing files to a read/write-enabled persistent partition
+ Given a computer
+ And I start Tails from USB drive "current" with network unplugged and I login with persistence password "asdf"
+ Then Tails is running from USB drive "current"
+ And the boot device has safe access rights
+ And persistence is enabled
And I write some files expected to persist
And persistent filesystems have safe access rights
And persistence configuration files have safe access rights
@@ -79,16 +93,9 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
@keep_volumes
Scenario: Writing files to a read-only-enabled persistent partition
Given a computer
- And the computer is set to boot from USB drive "current"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And Tails is running from USB drive "current"
+ And I start Tails from USB drive "current" with network unplugged and I login with read-only persistence password "asdf"
+ Then Tails is running from USB drive "current"
And the boot device has safe access rights
- And I enable read-only persistence with password "asdf"
- And I log in to a new session
- And GNOME has started
- And all notifications have disappeared
And persistence is enabled
And I write some files not expected to persist
And I remove some files expected to persist
@@ -98,14 +105,9 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
@keep_volumes
Scenario: Deleting a Tails persistent partition
Given a computer
- And the computer is set to boot from USB drive "current"
- And the network is unplugged
- And I start the computer
- And the computer boots Tails
- And I log in to a new session
- And Tails is running from USB drive "current"
+ And I start Tails from USB drive "current" with network unplugged and I login
+ Then Tails is running from USB drive "current"
And the boot device has safe access rights
- And Tails seems to have booted normally
And persistence is disabled
But a Tails persistence partition with password "asdf" exists on USB drive "current"
And all notifications have disappeared
@@ -132,14 +134,8 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
@keep_volumes
Scenario: Creating a persistent partition with the old Tails USB installation
Given a computer
- And the computer is set to boot from USB drive "old"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And Tails is running from USB drive "old"
- And I log in to a new session
- And GNOME has started
- And all notifications have disappeared
+ And I start Tails from USB drive "old" with network unplugged and I login
+ Then Tails is running from USB drive "old"
And I create a persistent partition with password "asdf"
Then a Tails persistence partition with password "asdf" exists on USB drive "old"
And I shutdown Tails and wait for the computer to power off
@@ -147,15 +143,8 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
@keep_volumes
Scenario: Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Given a computer
- And the computer is set to boot from USB drive "old"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And Tails is running from USB drive "old"
- And I enable persistence with password "asdf"
- And I log in to a new session
- And GNOME has started
- And all notifications have disappeared
+ And I start Tails from USB drive "old" with network unplugged and I login with persistence password "asdf"
+ Then Tails is running from USB drive "old"
And persistence is enabled
And I write some files expected to persist
And persistent filesystems have safe access rights
@@ -168,13 +157,7 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
Scenario: Upgrading an old Tails USB installation from a Tails DVD
Given a computer
And I clone USB drive "old" to a new USB drive "to_upgrade"
- And the computer is set to boot from the Tails DVD
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And I log in to a new session
- And GNOME has started
- And all notifications have disappeared
+ And I start Tails from DVD with network unplugged and I login
And I plug USB drive "to_upgrade"
And I "Clone & Upgrade" Tails to USB drive "to_upgrade"
Then the running Tails is installed on USB drive "to_upgrade"
@@ -183,14 +166,8 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
@keep_volumes
Scenario: Booting Tails from a USB drive upgraded from DVD with persistence enabled
Given a computer
- And the computer is set to boot from USB drive "to_upgrade"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And I enable persistence with password "asdf"
- And I log in to a new session
- Then Tails seems to have booted normally
- And Tails is running from USB drive "to_upgrade"
+ And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence password "asdf"
+ Then Tails is running from USB drive "to_upgrade"
And the boot device has safe access rights
And the expected persistent files are present in the filesystem
And persistent directories have safe access rights
@@ -199,15 +176,9 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
Scenario: Upgrading an old Tails USB installation from another Tails USB drive
Given a computer
And I clone USB drive "old" to a new USB drive "to_upgrade"
- And the computer is set to boot from USB drive "current"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And Tails is running from USB drive "current"
+ And I start Tails from USB drive "current" with network unplugged and I login
+ Then Tails is running from USB drive "current"
And the boot device has safe access rights
- And I log in to a new session
- And GNOME has started
- And all notifications have disappeared
And I plug USB drive "to_upgrade"
And I "Clone & Upgrade" Tails to USB drive "to_upgrade"
Then the running Tails is installed on USB drive "to_upgrade"
@@ -217,14 +188,8 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
@keep_volumes
Scenario: Booting Tails from a USB drive upgraded from USB with persistence enabled
Given a computer
- And the computer is set to boot from USB drive "to_upgrade"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And I enable persistence with password "asdf"
- And I log in to a new session
- Then Tails seems to have booted normally
- And persistence is enabled
+ And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence password "asdf"
+ Then persistence is enabled
And Tails is running from USB drive "to_upgrade"
And the boot device has safe access rights
And the expected persistent files are present in the filesystem
@@ -234,14 +199,8 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
Scenario: Upgrading an old Tails USB installation from an ISO image, running on the old version
Given a computer
And I clone USB drive "old" to a new USB drive "to_upgrade"
- And the computer is set to boot from USB drive "old"
- And the network is unplugged
And I setup a filesystem share containing the Tails ISO
- When I start the computer
- And the computer boots Tails
- And I log in to a new session
- And GNOME has started
- And all notifications have disappeared
+ When I start Tails from USB drive "old" with network unplugged and I login
And I plug USB drive "to_upgrade"
And I do a "Upgrade from ISO" on USB drive "to_upgrade"
Then the ISO's Tails is installed on USB drive "to_upgrade"
@@ -251,14 +210,8 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
Scenario: Upgrading an old Tails USB installation from an ISO image, running on the new version
Given a computer
And I clone USB drive "old" to a new USB drive "to_upgrade"
- And the computer is set to boot from the Tails DVD
- And the network is unplugged
And I setup a filesystem share containing the Tails ISO
- When I start the computer
- And the computer boots Tails
- And I log in to a new session
- And GNOME has started
- And all notifications have disappeared
+ And I start Tails from DVD with network unplugged and I login
And I plug USB drive "to_upgrade"
And I do a "Upgrade from ISO" on USB drive "to_upgrade"
Then the ISO's Tails is installed on USB drive "to_upgrade"
@@ -266,14 +219,8 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
Scenario: Booting a USB drive upgraded from ISO with persistence enabled
Given a computer
- And the computer is set to boot from USB drive "to_upgrade"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And I enable persistence with password "asdf"
- And I log in to a new session
- Then Tails seems to have booted normally
- And persistence is enabled
+ And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence password "asdf"
+ Then persistence is enabled
And Tails is running from USB drive "to_upgrade"
And the boot device has safe access rights
And the expected persistent files are present in the filesystem
@@ -284,13 +231,7 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
Given a computer
And I create a 4 GiB disk named "mbr"
And I create a msdos label on disk "mbr"
- And the computer is set to boot from the Tails DVD
- And the network is unplugged
- And I start the computer
- When the computer boots Tails
- And I log in to a new session
- And GNOME has started
- And all notifications have disappeared
+ And I start Tails from DVD with network unplugged and I login
And I plug USB drive "mbr"
And I "Clone & Install" Tails to USB drive "mbr"
Then the running Tails is installed on USB drive "mbr"
@@ -299,13 +240,8 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
Scenario: Booting a USB drive that originally had an empty MBR partition table
Given a computer
- And the computer is set to boot from USB drive "mbr"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And I log in to a new session
- Then Tails seems to have booted normally
- And Tails is running from USB drive "mbr"
+ And I start Tails from USB drive "mbr" with network unplugged and I login
+ Then Tails is running from USB drive "mbr"
And the boot device has safe access rights
And there is no persistence partition on USB drive "mbr"
@@ -314,24 +250,13 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
Given a computer
And I create a 4 GiB disk named "isohybrid"
And I cat an ISO hybrid of the Tails image to disk "isohybrid"
- And the computer is set to boot from USB drive "isohybrid"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And I log in to a new session
- Then Tails seems to have booted normally
- And Tails is running from USB drive "isohybrid"
+ And I start Tails from USB drive "isohybrid" with network unplugged and I login
+ Then Tails is running from USB drive "isohybrid"
@keep_volumes
Scenario: Try upgrading but end up installing Tails to a USB drive containing a Tails isohybrid installation
Given a computer
- And the computer is set to boot from the Tails DVD
- And the network is unplugged
- And I start the computer
- When the computer boots Tails
- And I log in to a new session
- And GNOME has started
- And all notifications have disappeared
+ And I start Tails from DVD with network unplugged and I login
And I plug USB drive "isohybrid"
And I try a "Clone & Upgrade" Tails to USB drive "isohybrid"
But I am suggested to do a "Clone & Install"
@@ -343,12 +268,7 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
Scenario: Booting a USB drive that originally had a isohybrid installation
Given a computer
- And the computer is set to boot from USB drive "isohybrid"
- And the network is unplugged
- When I start the computer
- And the computer boots Tails
- And I log in to a new session
- Then Tails seems to have booted normally
- And Tails is running from USB drive "isohybrid"
+ And I start Tails from USB drive "isohybrid" with network unplugged and I login
+ Then Tails is running from USB drive "isohybrid"
And the boot device has safe access rights
And there is no persistence partition on USB drive "isohybrid"