Project Number Date
test_Tails_ISO_20950-remove-sshfs 2 14 May 2025, 00:54

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:50.367 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:2.257
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.051
When I start Tails from USB drive "old" with network unplugged 1:25.910
Then the boot device has safe access rights 3.058
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 3.769
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.060
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:33.672
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 33.300
And I take note of which tps features are available 1.683
Then a Tails persistence partition exists on USB drive "old" 0.762
And I shutdown Tails and wait for the computer to power off 8.149
After features/support/hooks.rb:330 0.192
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.193
Then Tails is running from USB drive "old" 0.320
And all tps features are active 1.968
When I write some files expected to persist 1.550
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.236
And I take note of which tps features are available 0.410
And I shutdown Tails and wait for the computer to power off 4.273
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.782
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.099
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 without a persistent partition and stopped at Tails Greeter's login screen 10.054
And I log in to a new session 17.865
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.752
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.721
Then the running Tails is installed on USB drive "to_upgrade" 23.872
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:330 1.783
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.160
Then all tps features from the old Tails version are active 1.542
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.383
And the expected persistent files created with the old Tails version are present in the filesystem 1.415
And all persistent directories from the old Tails version have safe access rights 2.404
After features/support/hooks.rb:330 1.251
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:26.752
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.938
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.088
And Tor is ready 19.021
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.016
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.948
Given I shutdown Tails and wait for the computer to power off 8.433
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.916
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.124
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# 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.312
When the network is plugged 0.062
And Tor is ready 19.036
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.267
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.740
Given I shutdown Tails and wait for the computer to power off 4.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.392
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.864
And the file system changes introduced in version 6.3~testoverlayfs are present 0.464
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.336
When the network is plugged 0.067
And Tor is ready 17.949
Then the Upgrader considers the system as up-to-date 10.854
# 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.311
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.959
After features/support/hooks.rb:330 0.717
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
34.277
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 9.381
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the signing key used by the Upgrader is outdated 0.136
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 17.853
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.415
After features/support/hooks.rb:330 0.813
After features/support/hooks.rb:100 0.000