Project Number Date
test_Tails_ISO_stable 4714 13 Mar 2024, 15:12

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 18:40.144 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.851
Before features/support/hooks.rb:245 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 19.416
When I start Tails from USB drive "old" with network unplugged 1:13.086
Then the boot device has safe access rights 3.113
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:291 7.006
After features/support/hooks.rb:75 0.011
Tags: @product
2:15.064
Before features/support/hooks.rb:245 0.007
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:22.215
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 42.515
And I take note of which tps features are available 2.049
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 7.042
After features/support/hooks.rb:291 0.153
After features/support/hooks.rb:75 0.009
Tags: @product
2:44.531
Before features/support/hooks.rb:245 0.006
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.304
Then Tails is running from USB drive "old" 0.315
And all tps features are active 1.796
When I write some files expected to persist 1.560
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.427
And I take note of which tps features are available 0.316
And I shutdown Tails and wait for the computer to power off 3.134
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.898
After features/support/hooks.rb:291 0.193
After features/support/hooks.rb:75 0.010
Tags: @product
2:27.739
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.530
And I log in to a new session 16.793
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.285
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.588
Then the running Tails is installed on USB drive "to_upgrade" 13.750
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:291 3.531
After features/support/hooks.rb:75 0.000
Tags: @product
2:16.111
Before features/support/hooks.rb:245 0.006
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.585
Then all tps features from the old Tails version are active 1.350
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.051
And the expected persistent files created with the old Tails version are present in the filesystem 1.387
And all persistent directories from the old Tails version have safe access rights 2.262
After features/support/hooks.rb:291 0.593
After features/support/hooks.rb:75 0.041
Tags: @product @automatic_upgrade
6:44.576
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.600
And no SquashFS delta is installed 0.241
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.028
And Tor is ready 19.235
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.369
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.071
Given I shutdown Tails and wait for the computer to power off 7.200
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.956
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.832
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# 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.260
When the network is plugged 0.028
And Tor is ready 17.995
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.028
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.279
Given I shutdown Tails and wait for the computer to power off 4.029
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.250
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.810
And the file system changes introduced in version 6.3~testoverlayfs are present 0.441
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.036
And Tor is ready 17.239
Then the Upgrader considers the system as up-to-date 10.619
# 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.654
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.867
After features/support/hooks.rb:291 0.685
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
34.269
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.413
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.528
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 17.551
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.278
After features/support/hooks.rb:291 0.852
After features/support/hooks.rb:75 0.000