Project Number Date
test_Tails_ISO_stable 4651 05 Feb 2024, 12:24

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 88 0 0 0 0 88 7 0 7 18:57.484 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
1:37.258
Before features/support/hooks.rb:245 0.004
Given a computer 0.150
And I create a 7200 MiB disk named "old" 0.033
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 20.211
When I start Tails from USB drive "old" with network unplugged 1:11.867
Then the boot device has safe access rights 2.882
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.394
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:291 6.729
After features/support/hooks.rb:75 0.007
Tags: @product
2:12.793
Before features/support/hooks.rb:245 0.004
Given a computer 0.144
And I start Tails from USB drive "old" with network unplugged and I login 1:20.145
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 41.497
And I take note of which tps features are available 1.777
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 8.087
After features/support/hooks.rb:291 0.209
After features/support/hooks.rb:75 0.008
Tags: @product
2:44.440
Before features/support/hooks.rb:245 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.440
Then Tails is running from USB drive "old" 0.311
And all tps features are active 1.791
When I write some files expected to persist 1.593
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.641
And all persistent directories from the old Tails version have safe access rights 2.297
And I take note of which tps features are available 0.378
And I shutdown Tails and wait for the computer to power off 4.048
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.559
After features/support/hooks.rb:291 0.168
After features/support/hooks.rb:75 0.010
Tags: @product
2:34.568
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.871
And I log in to a new session 18.556
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.257
And I plug USB drive "to_upgrade" 2.486
And I cancel the GNOME authentication prompt 1.675
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.977
Then the running Tails is installed on USB drive "to_upgrade" 13.380
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:291 3.579
After features/support/hooks.rb:75 0.000
Tags: @product
2:26.838
Before features/support/hooks.rb:245 0.005
Given a computer 0.142
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.402
Then all tps features from the old Tails version are active 1.549
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 2.851
And the expected persistent files created with the old Tails version are present in the filesystem 1.240
And all persistent directories from the old Tails version have safe access rights 2.312
After features/support/hooks.rb:291 0.596
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:30.578
Before features/support/hooks.rb:245 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.940
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.381
When the network is plugged 0.045
And Tor is ready 18.115
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.961
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.499
Given I shutdown Tails and wait for the computer to power off 7.510
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.748
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.075
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.067
And Tor is ready 18.562
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.639
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.009
Given I shutdown Tails and wait for the computer to power off 4.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.914
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.878
And the file system changes introduced in version 6.3~testoverlayfs are present 0.574
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.058
And Tor is ready 18.128
Then the Upgrader considers the system as up-to-date 0.227
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 13.614
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.882
After features/support/hooks.rb:291 0.653
After features/support/hooks.rb:75 0.030
Tags: @product @automatic_upgrade
51.007
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.770
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.485
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 39.823
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.550
After features/support/hooks.rb:291 0.647
After features/support/hooks.rb:75 0.000