Project Number Date
test_Tails_ISO_20950-remove-sshfs 5 16 May 2025, 23:42

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:12.760 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:24.940
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.239
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.522
When I start Tails from USB drive "old" with network unplugged 1:46.835
Then the boot device has safe access rights 3.091
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.092
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.246
After features/support/hooks.rb:330 3.764
After features/support/hooks.rb:100 0.010
Tags: @product
2:19.738
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:36.144
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 31.763
And I take note of which tps features are available 1.881
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.530
After features/support/hooks.rb:330 0.239
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.045
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.307
Then Tails is running from USB drive "old" 0.461
And all tps features are active 2.174
When I write some files expected to persist 1.711
# 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.377
And all persistent directories from the old Tails version have safe access rights 2.518
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 6.423
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.168
After features/support/hooks.rb:330 0.097
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.461
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 10.375
And I log in to a new session 19.000
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.756
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.900
Then the running Tails is installed on USB drive "to_upgrade" 25.495
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.259
After features/support/hooks.rb:330 1.797
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.173
Then all tps features from the old Tails version are active 1.975
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.905
And the expected persistent files created with the old Tails version are present in the filesystem 1.470
And all persistent directories from the old Tails version have safe access rights 2.751
After features/support/hooks.rb:330 1.094
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:59.149
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 19.837
And no SquashFS delta is installed 0.340
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.461
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.066
And Tor is ready 23.262
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.064
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.260
Given I shutdown Tails and wait for the computer to power off 13.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.309
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.200
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.292
When the network is plugged 0.070
And Tor is ready 20.104
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.012
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.100
Given I shutdown Tails and wait for the computer to power off 4.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.008
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.995
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.402
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.075
And Tor is ready 19.765
Then the Upgrader considers the system as up-to-date 0.316
# 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.239
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.648
After features/support/hooks.rb:330 0.738
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.634
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 with a persistent partition enabled and logged in 12.030
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.623
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 20.139
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.601
After features/support/hooks.rb:330 0.727
After features/support/hooks.rb:100 0.000