Project Number Date
test_Tails_ISO_20950-remove-sshfs 3 14 May 2025, 23: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 20:27.665 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:12.613
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 31.153
When I start Tails from USB drive "old" with network unplugged 1:36.100
Then the boot device has safe access rights 3.052
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:330 3.742
After features/support/hooks.rb:100 0.021
Tags: @product
2:24.562
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.284
And I start Tails from USB drive "old" with network unplugged and I login 1:40.437
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 32.655
And I take note of which tps features are available 1.678
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.332
After features/support/hooks.rb:330 0.180
After features/support/hooks.rb:100 0.011
Tags: @product
3:2.022
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.987
Then Tails is running from USB drive "old" 0.381
And all tps features are active 2.236
When I write some files expected to persist 1.735
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.555
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 6.744
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.051
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.967
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 14.441
And I log in to a new session 21.744
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.825
And I plug USB drive "to_upgrade" 2.605
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.427
Then the running Tails is installed on USB drive "to_upgrade" 25.419
And I unplug USB drive "to_upgrade" 0.301
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 3.608
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.470
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.237
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.989
Then all tps features from the old Tails version are active 1.714
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 3.900
And the expected persistent files created with the old Tails version are present in the filesystem 1.627
And all persistent directories from the old Tails version have safe access rights 2.639
After features/support/hooks.rb:330 1.575
After features/support/hooks.rb:100 0.009
7:4.186
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.026
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.611
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.425
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.139
And Tor is ready 24.779
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.645
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.779
Given I shutdown Tails and wait for the computer to power off 8.593
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.739
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.909
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.264
When the network is plugged 0.071
And Tor is ready 20.015
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.027
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.032
Given I shutdown Tails and wait for the computer to power off 4.447
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.399
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.180
And the file system changes introduced in version 6.3~testoverlayfs are present 0.579
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.382
When the network is plugged 0.078
And Tor is ready 19.381
Then the Upgrader considers the system as up-to-date 0.333
# 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.662
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.817
After features/support/hooks.rb:330 0.737
After features/support/hooks.rb:100 0.020
36.843
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.739
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.105
And the signing key used by the Upgrader is outdated 0.128
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 18.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.057
After features/support/hooks.rb:330 2.424
After features/support/hooks.rb:100 0.000