Project Number Date
test_Tails_ISO_stable 4711 12 Mar 2024, 12:15

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:56.779 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:35.650
Before features/support/hooks.rb:245 0.007
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 21.190
When I start Tails from USB drive "old" with network unplugged 1:9.017
Then the boot device has safe access rights 3.152
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:291 6.691
After features/support/hooks.rb:75 0.010
Tags: @product
2:8.691
Before features/support/hooks.rb:245 0.006
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:16.670
Then Tails is running from USB drive "old" 0.296
And I create a persistent partition 40.959
And I take note of which tps features are available 1.658
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 8.115
After features/support/hooks.rb:291 0.184
After features/support/hooks.rb:75 0.010
Tags: @product
2:45.851
Before features/support/hooks.rb:245 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.917
Then Tails is running from USB drive "old" 0.379
And all tps features are active 2.059
When I write some files expected to persist 1.669
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.282
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 2.283
And I take note of which tps features are available 0.430
And I shutdown Tails and wait for the computer to power off 4.017
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.143
After features/support/hooks.rb:291 0.107
After features/support/hooks.rb:75 0.010
Tags: @product
2:30.844
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.875
And I log in to a new session 15.013
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.199
And I plug USB drive "to_upgrade" 2.391
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.737
Then the running Tails is installed on USB drive "to_upgrade" 13.159
And I unplug USB drive "to_upgrade" 0.260
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:291 6.534
After features/support/hooks.rb:75 0.000
Tags: @product
2:20.053
Before features/support/hooks.rb:245 0.007
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.403
Then all tps features from the old Tails version are active 1.437
And Tails is running from USB drive "to_upgrade" 0.287
And the boot device has safe access rights 3.006
And the expected persistent files created with the old Tails version are present in the filesystem 1.464
And all persistent directories from the old Tails version have safe access rights 2.269
After features/support/hooks.rb:291 0.600
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:37.585
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 11.743
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.040
And Tor is ready 21.105
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.041
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.098
Given I shutdown Tails and wait for the computer to power off 6.119
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.923
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.897
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.378
# 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.291
When the network is plugged 0.032
And Tor is ready 14.890
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.692
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.731
Given I shutdown Tails and wait for the computer to power off 4.030
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.410
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.792
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.352
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.045
And Tor is ready 17.708
Then the Upgrader considers the system as up-to-date 0.249
# 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.625
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.927
After features/support/hooks.rb:291 0.781
After features/support/hooks.rb:75 0.024
Tags: @product @automatic_upgrade
58.102
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.356
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
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.041
And Tor is ready 45.225
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.594
After features/support/hooks.rb:291 0.619
After features/support/hooks.rb:75 0.000