Project Number Date
test_Tails_ISO_20950-remove-sshfs 4 16 May 2025, 00:03

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:49.263 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:13.350
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.887
When I start Tails from USB drive "old" with network unplugged 1:36.781
Then the boot device has safe access rights 3.350
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:330 3.759
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.552
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:35.118
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 33.729
And I take note of which tps features are available 1.844
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 8.538
After features/support/hooks.rb:330 0.265
After features/support/hooks.rb:100 0.009
Tags: @product
3:4.788
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.175
Then Tails is running from USB drive "old" 0.338
And all tps features are active 2.204
When I write some files expected to persist 1.686
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.407
And I take note of which tps features are available 0.414
And I shutdown Tails and wait for the computer to power off 4.343
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.358
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.864
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 23.978
And I log in to a new session 18.984
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.034
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.461
Then the running Tails is installed on USB drive "to_upgrade" 20.413
And I unplug USB drive "to_upgrade" 0.350
And I unplug USB drive "__internal" 0.265
After features/support/hooks.rb:330 2.382
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.841
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.962
Then all tps features from the old Tails version are active 1.660
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.618
And the expected persistent files created with the old Tails version are present in the filesystem 1.565
And all persistent directories from the old Tails version have safe access rights 2.532
After features/support/hooks.rb:330 1.202
After features/support/hooks.rb:100 0.008
6:32.515
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 10.936
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.742
When the network is plugged 0.060
And Tor is ready 21.068
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.068
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.877
Given I shutdown Tails and wait for the computer to power off 9.132
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.926
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.058
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.278
When the network is plugged 0.072
And Tor is ready 17.443
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.176
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.735
Given I shutdown Tails and wait for the computer to power off 4.456
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.198
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.020
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.078
And Tor is ready 18.318
Then the Upgrader considers the system as up-to-date 0.329
# 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 16.639
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.194
After features/support/hooks.rb:330 0.738
After features/support/hooks.rb:100 0.017
40.350
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 10.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.119
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 20.496
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.049
After features/support/hooks.rb:330 0.809
After features/support/hooks.rb:100 0.000