Project Number Date
test_Tails_ISO_devel 3470 08 Aug 2024, 15:40

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 19:41.043 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
2:10.364
Before features/support/hooks.rb:269 0.007
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.828
When I start Tails from USB drive "old" with network unplugged 1:33.976
Then the boot device has safe access rights 3.246
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 6.977
After features/support/hooks.rb:100 0.011
Tags: @product
2:15.513
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:29.085
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 35.230
And I take note of which tps features are available 1.475
Then a Tails persistence partition exists on USB drive "old" 0.870
And I shutdown Tails and wait for the computer to power off 8.307
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.011
Tags: @product
2:52.065
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.097
Then Tails is running from USB drive "old" 0.360
And all tps features are active 1.911
When I write some files expected to persist 1.787
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.605
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 4.426
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.504
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.012
Tags: @product
2:32.372
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.794
And I log in to a new session 19.229
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.013
And I plug USB drive "to_upgrade" 2.394
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.458
Then the running Tails is installed on USB drive "to_upgrade" 19.071
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 3.994
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.627
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.735
Then all tps features from the old Tails version are active 1.705
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.358
And the expected persistent files created with the old Tails version are present in the filesystem 1.872
And all persistent directories from the old Tails version have safe access rights 2.432
After features/support/hooks.rb:326 0.821
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:1.105
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.913
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.063
And Tor is ready 21.137
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.571
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.072
Given I shutdown Tails and wait for the computer to power off 13.413
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.445
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.981
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.271
When the network is plugged 0.102
And Tor is ready 17.287
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.782
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.910
Given I shutdown Tails and wait for the computer to power off 4.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.343
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.108
# 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.368
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.063
And Tor is ready 18.361
Then the Upgrader considers the system as up-to-date 0.344
# 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 14.058
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.065
After features/support/hooks.rb:326 0.826
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
36.994
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.765
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.935
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.066
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.690
After features/support/hooks.rb:326 0.695
After features/support/hooks.rb:100 0.000