Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
tails
tails
Commits
aeecb3e9
Commit
aeecb3e9
authored
May 13, 2015
by
anonym
Browse files
Split usb_install.feature and move scenarios where more appropriate.
parent
b1518279
Changes
4
Hide whitespace changes
Inline
Side-by-side
features/persistence.feature
0 → 100644
View file @
aeecb3e9
@product
Feature
:
Tails persistence
As a Tails user
I want use Tails persistence feature
Scenario
:
Booting Tails from a USB drive with a disabled persistent partition
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
When
I log in to a new session
Then
Tails seems to have booted normally
And
Tails is running from USB drive
"current"
And
persistence is disabled
But
a Tails persistence partition with password
"asdf"
exists on USB drive
"current"
Scenario
:
Booting Tails from a USB drive with an enabled persistent partition
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
When
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
"current"
And
all persistence presets are enabled
And
all persistent directories have safe access rights
Scenario
:
Writing files to a read/write-enabled persistent partition
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
When
I enable persistence with password
"asdf"
And
I log in to a new session
Then
Tails is running from USB drive
"current"
And
the boot device has safe access rights
And
all persistence presets are enabled
And
I write some files expected to persist
And
all persistent filesystems have safe access rights
And
all persistence configuration files have safe access rights
And
all persistent directories have safe access rights
And
I take note of which persistence presets are available
And
I shutdown Tails and wait for the computer to power off
# XXX: how does guestfs work vs snapshots?
Then
only the expected files are present on the persistence partition encrypted with password
"asdf"
on USB drive
"current"
Scenario
:
Writing files to a read-only-enabled persistent partition
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
When
I enable read-only persistence with password
"asdf"
And
I log in to a new session
Then
Tails is running from USB drive
"current"
And
the boot device has safe access rights
And
all persistence presets are enabled
And
there is no GNOME bookmark for the persistent Tor Browser directory
And
I write some files not expected to persist
And
I remove some files expected to persist
And
I take note of which persistence presets are available
And
I shutdown Tails and wait for the computer to power off
# XXX: how does guestfs work vs snapshots?
Then
only the expected files are present on the persistence partition encrypted with password
"asdf"
on USB drive
"current"
Scenario
:
Deleting a Tails persistent partition
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
And
I log in to a new session
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"
And
all notifications have disappeared
When
I delete the persistent partition
Then
there is no persistence partition on USB drive
"current"
features/torified_browsing.feature
View file @
aeecb3e9
...
...
@@ -83,3 +83,45 @@ Feature: Browsing the web using the Tor Browser
When
I start the Tor Browser
And
the Tor Browser has started and loaded the startup page
Then
the Tor Browser has no plugins installed
Scenario
:
The persistent Tor Browser directory is usable
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
And
the network is plugged
When
I enable persistence with password
"asdf"
And
I log in to a new session
And
Tails is running from USB drive
"current"
And
Tor is ready
And
available upgrades have been checked
And
all notifications have disappeared
Then
the persistent Tor Browser directory exists
And
there is a GNOME bookmark for the persistent Tor Browser directory
When
I start the Tor Browser
And
the Tor Browser has started and loaded the startup page
And
I can save the current page as
"index.html"
to the persistent Tor Browser directory
When I open the address "file
:
///home/amnesia/Persistent/Tor
Browser/index.html"
in
the
Tor
Browser
Then
I see
"TorBrowserSavedStartupPage.png"
after at most 10 seconds
And
I can print the current page as
"output.pdf"
to the persistent Tor Browser directory
Scenario
:
Persistent browser bookmarks
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
And
Tails is running from USB drive
"current"
And
the boot device has safe access rights
And
I enable persistence with password
"asdf"
And
I log in to a new session
And
the Tails desktop is ready
And
all notifications have disappeared
And
all persistence presets are enabled
And
all persistent filesystems have safe access rights
And
all persistence configuration files have safe access rights
And
all 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
the Tails desktop is ready
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
features/usb_install.feature
View file @
aeecb3e9
@product
@old_iso
Feature
:
Installing Tails to a USB drive
, upgrading it, and using persistence
@product
Feature
:
Installing Tails to a USB drive
As a Tails user
I may want to install Tails to a USB drive
and upgrade it to new Tails versions
and use persistence
I want to install Tails to a suitable USB drive
Scenario
:
Try installing Tails to a too small USB drive
Given
Tails has booted from DVD without network and logged in
...
...
@@ -43,214 +41,6 @@ Feature: Installing Tails to a USB drive, upgrading it, and using persistence
And
the boot device has safe access rights
And
Tails has started in UEFI mode
Scenario
:
Booting Tails from a USB drive with a disabled persistent partition
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
When
I log in to a new session
Then
Tails seems to have booted normally
And
Tails is running from USB drive
"current"
And
persistence is disabled
But
a Tails persistence partition with password
"asdf"
exists on USB drive
"current"
Scenario
:
The persistent Tor Browser directory is usable
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
And
the network is plugged
When
I enable persistence with password
"asdf"
And
I log in to a new session
And
Tails is running from USB drive
"current"
And
Tor is ready
And
available upgrades have been checked
And
all notifications have disappeared
Then
the persistent Tor Browser directory exists
And
there is a GNOME bookmark for the persistent Tor Browser directory
When
I start the Tor Browser
And
the Tor Browser has started and loaded the startup page
And
I can save the current page as
"index.html"
to the persistent Tor Browser directory
When I open the address "file
:
///home/amnesia/Persistent/Tor
Browser/index.html"
in
the
Tor
Browser
Then
I see
"TorBrowserSavedStartupPage.png"
after at most 10 seconds
And
I can print the current page as
"output.pdf"
to the persistent Tor Browser directory
Scenario
:
Persistent browser bookmarks
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
And
Tails is running from USB drive
"current"
And
the boot device has safe access rights
And
I enable persistence with password
"asdf"
And
I log in to a new session
And
the Tails desktop is ready
And
all notifications have disappeared
And
all persistence presets are enabled
And
all persistent filesystems have safe access rights
And
all persistence configuration files have safe access rights
And
all 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
the Tails desktop is ready
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
Scenario
:
Booting Tails from a USB drive with an enabled persistent partition
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
When
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
"current"
And
all persistence presets are enabled
And
all persistent directories have safe access rights
Scenario
:
Writing files to a read/write-enabled persistent partition
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
When
I enable persistence with password
"asdf"
And
I log in to a new session
Then
Tails is running from USB drive
"current"
And
the boot device has safe access rights
And
all persistence presets are enabled
And
I write some files expected to persist
And
all persistent filesystems have safe access rights
And
all persistence configuration files have safe access rights
And
all persistent directories have safe access rights
And
I take note of which persistence presets are available
And
I shutdown Tails and wait for the computer to power off
# XXX: how does guestfs work vs snapshots?
Then
only the expected files are present on the persistence partition encrypted with password
"asdf"
on USB drive
"current"
Scenario
:
Writing files to a read-only-enabled persistent partition
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
When
I enable read-only persistence with password
"asdf"
And
I log in to a new session
Then
Tails is running from USB drive
"current"
And
the boot device has safe access rights
And
all persistence presets are enabled
And
there is no GNOME bookmark for the persistent Tor Browser directory
And
I write some files not expected to persist
And
I remove some files expected to persist
And
I take note of which persistence presets are available
And
I shutdown Tails and wait for the computer to power off
# XXX: how does guestfs work vs snapshots?
Then
only the expected files are present on the persistence partition encrypted with password
"asdf"
on USB drive
"current"
Scenario
:
Deleting a Tails persistent partition
Given
Tails has booted without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
And
I log in to a new session
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"
And
all notifications have disappeared
When
I delete the persistent partition
Then
there is no persistence partition on USB drive
"current"
Scenario
:
Installing an old version of Tails to a pristine USB drive
Given
a computer
And
the computer is set to boot from the old 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
the Tails desktop is ready
And
all notifications have disappeared
And
I create a 4 GiB disk named
"old"
And
I plug USB drive
"old"
And
I
"Clone & Install"
Tails to USB drive
"old"
Then
the running Tails is installed on USB drive
"old"
But
there is no persistence partition on USB drive
"old"
And
I unplug USB drive
"old"
Scenario
:
Creating a persistent partition with the old Tails USB installation
Given
a computer
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"
And
I take note of which persistence presets are available
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
Scenario
:
Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Given
a computer
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
all persistence presets are enabled
And
I write some files expected to persist
And
all persistent filesystems have safe access rights
And
all persistence configuration files have safe access rights
And
all persistent directories from the old Tails version have safe access rights
And
I take note of which persistence presets are available
And
I shutdown Tails and wait for the computer to power off
# XXX: how does guestfs work vs snapshots?
Then
only the expected files are present on the persistence partition encrypted with password
"asdf"
on USB drive
"old"
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
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"
And
I unplug USB drive
"to_upgrade"
Scenario
:
Booting Tails from a USB drive upgraded from DVD with persistence enabled
Given
a computer
And
I start Tails from USB drive
"to_upgrade"
with network unplugged and I login with persistence password
"asdf"
Then
all persistence presets from the old Tails version are enabled
Then
Tails is running from USB drive
"to_upgrade"
And
the boot device has safe access rights
And
the expected persistent files created with the old Tails version are present in the filesystem
And
all persistent directories from the old Tails version have safe access rights
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
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 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"
And
I unplug USB drive
"to_upgrade"
And
I unplug USB drive
"current"
Scenario
:
Booting Tails from a USB drive upgraded from USB with persistence enabled
Given
a computer
And
I start Tails from USB drive
"to_upgrade"
with network unplugged and I login with persistence password
"asdf"
Then
all persistence presets from the old Tails version are enabled
And
Tails is running from USB drive
"to_upgrade"
And
the boot device has safe access rights
And
the expected persistent files created with the old Tails version are present in the filesystem
And
all persistent directories from the old Tails version have safe access rights
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
I setup a filesystem share containing the Tails ISO
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"
And
I unplug USB drive
"to_upgrade"
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
I setup a filesystem share containing the Tails ISO
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"
And
I unplug USB drive
"to_upgrade"
Scenario
:
Booting a USB drive upgraded from ISO with persistence enabled
Given
a computer
And
I start Tails from USB drive
"to_upgrade"
with network unplugged and I login with persistence password
"asdf"
Then
all persistence presets from the old Tails version are enabled
And
Tails is running from USB drive
"to_upgrade"
And
the boot device has safe access rights
And
the expected persistent files created with the old Tails version are present in the filesystem
And
all persistent directories from the old Tails version have safe access rights
Scenario
:
Installing Tails to a USB drive with an MBR partition table but no partitions, and making sure that it boots
Given
a computer
And
I temporarily create a 4 GiB disk named
"mbr"
...
...
features/usb_upgrade.feature
0 → 100644
View file @
aeecb3e9
@product
@old_iso
Feature
:
Installing Tails to a USB drive
As a Tails user
If I have an old versoin of Tails installed on a USB device
and the USB device has a persistent partition
I want to upgrade Tails on it
and keep my persistent partition in the process
Scenario
:
Installing an old version of Tails to a pristine USB drive
Given
a computer
And
the computer is set to boot from the old 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
the Tails desktop is ready
And
all notifications have disappeared
And
I create a 4 GiB disk named
"old"
And
I plug USB drive
"old"
And
I
"Clone & Install"
Tails to USB drive
"old"
Then
the running Tails is installed on USB drive
"old"
But
there is no persistence partition on USB drive
"old"
And
I unplug USB drive
"old"
Scenario
:
Creating a persistent partition with the old Tails USB installation
Given
a computer
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"
And
I take note of which persistence presets are available
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
Scenario
:
Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Given
a computer
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
all persistence presets are enabled
And
I write some files expected to persist
And
all persistent filesystems have safe access rights
And
all persistence configuration files have safe access rights
And
all persistent directories from the old Tails version have safe access rights
And
I take note of which persistence presets are available
And
I shutdown Tails and wait for the computer to power off
# XXX: how does guestfs work vs snapshots?
Then
only the expected files are present on the persistence partition encrypted with password
"asdf"
on USB drive
"old"
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
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"
And
I unplug USB drive
"to_upgrade"
Scenario
:
Booting Tails from a USB drive upgraded from DVD with persistence enabled
Given
a computer
And
I start Tails from USB drive
"to_upgrade"
with network unplugged and I login with persistence password
"asdf"
Then
all persistence presets from the old Tails version are enabled
Then
Tails is running from USB drive
"to_upgrade"
And
the boot device has safe access rights
And
the expected persistent files created with the old Tails version are present in the filesystem
And
all persistent directories from the old Tails version have safe access rights
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
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 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"
And
I unplug USB drive
"to_upgrade"
And
I unplug USB drive
"current"
Scenario
:
Booting Tails from a USB drive upgraded from USB with persistence enabled
Given
a computer
And
I start Tails from USB drive
"to_upgrade"
with network unplugged and I login with persistence password
"asdf"
Then
all persistence presets from the old Tails version are enabled
And
Tails is running from USB drive
"to_upgrade"
And
the boot device has safe access rights
And
the expected persistent files created with the old Tails version are present in the filesystem
And
all persistent directories from the old Tails version have safe access rights
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
I setup a filesystem share containing the Tails ISO
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"
And
I unplug USB drive
"to_upgrade"
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
I setup a filesystem share containing the Tails ISO
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"
And
I unplug USB drive
"to_upgrade"
Scenario
:
Booting a USB drive upgraded from ISO with persistence enabled
Given
a computer
And
I start Tails from USB drive
"to_upgrade"
with network unplugged and I login with persistence password
"asdf"
Then
all persistence presets from the old Tails version are enabled
And
Tails is running from USB drive
"to_upgrade"
And
the boot device has safe access rights
And
the expected persistent files created with the old Tails version are present in the filesystem
And
all persistent directories from the old Tails version have safe access rights
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment