Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 9 20 Apr 2025, 21:14

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:20.006 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:16.008
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.656
When I start Tails from USB drive "old" with network unplugged 1:39.819
Then the boot device has safe access rights 3.244
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 7.351
After features/support/hooks.rb:100 0.012
Tags: @product
2:14.140
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:30.828
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 31.252
And I take note of which tps features are available 2.261
Then a Tails persistence partition exists on USB drive "old" 0.737
And I shutdown Tails and wait for the computer to power off 8.472
After features/support/hooks.rb:330 0.216
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.662
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.273
Then Tails is running from USB drive "old" 1.083
And all tps features are active 2.198
When I write some files expected to persist 1.716
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.536
And I take note of which tps features are available 0.605
And I shutdown Tails and wait for the computer to power off 4.244
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.209
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.042
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 11.066
And I log in to a new session 20.115
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.576
And I plug USB drive "to_upgrade" 2.465
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.355
Then the running Tails is installed on USB drive "to_upgrade" 23.003
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.266
After features/support/hooks.rb:330 0.772
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.468
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.573
Then all tps features from the old Tails version are active 1.645
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.669
And the expected persistent files created with the old Tails version are present in the filesystem 1.513
And all persistent directories from the old Tails version have safe access rights 2.509
After features/support/hooks.rb:330 1.215
After features/support/hooks.rb:100 0.008
6:34.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.555
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.131
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.373
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.075
And Tor is ready 22.447
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.188
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.055
Given I shutdown Tails and wait for the computer to power off 11.147
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.962
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.262
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.354
When the network is plugged 0.069
And Tor is ready 20.012
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.896
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.957
Given I shutdown Tails and wait for the computer to power off 4.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.666
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.210
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.291
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.069
And Tor is ready 16.056
Then the Upgrader considers the system as up-to-date 0.315
# 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 15.981
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.748
After features/support/hooks.rb:330 0.803
After features/support/hooks.rb:100 0.035
36.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.273
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.256
And Tor is ready 18.290
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.854
After features/support/hooks.rb:330 1.119
After features/support/hooks.rb:100 0.000