Project Number Date
test_Tails_ISO_devel 3879 22 Jun 2025, 13:47

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 24:40.917 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:57.282
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.292
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 40.492
When I start Tails from USB drive "old" with network unplugged 2:9.715
Then the boot device has safe access rights 4.543
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.126
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:330 8.589
After features/support/hooks.rb:100 0.087
Tags: @product
3:2.671
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.115
Given a computer 0.726
And I start Tails from USB drive "old" with network unplugged and I login 2:2.126
Then Tails is running from USB drive "old" 1.800
And I create a persistent partition 42.282
And I take note of which tps features are available 2.931
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 12.023
After features/support/hooks.rb:330 0.610
After features/support/hooks.rb:100 0.038
Tags: @product
4:5.338
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.031
Given a computer 0.468
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:7.481
Then Tails is running from USB drive "old" 0.595
And all tps features are active 2.341
When I write some files expected to persist 2.259
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.542
And all persistent directories from the old Tails version have safe access rights 9.590
And I take note of which tps features are available 0.603
And I shutdown Tails and wait for the computer to power off 4.197
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 37.013
After features/support/hooks.rb:330 0.109
After features/support/hooks.rb:100 0.009
Tags: @product
3:6.961
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.048
And I log in to a new session 30.603
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.511
And I plug USB drive "to_upgrade" 2.461
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.269
Then the running Tails is installed on USB drive "to_upgrade" 30.660
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:330 7.495
After features/support/hooks.rb:100 0.000
Tags: @product
2:44.280
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.283
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:31.062
Then all tps features from the old Tails version are active 1.889
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 5.392
And the expected persistent files created with the old Tails version are present in the filesystem 2.086
And all persistent directories from the old Tails version have safe access rights 3.200
After features/support/hooks.rb:330 1.857
After features/support/hooks.rb:100 0.010
8:1.566
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 13.991
And no SquashFS delta is installed 0.149
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.491
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.566
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.111
When the network is plugged 0.077
And Tor is ready 24.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.273
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.682
Given I shutdown Tails and wait for the computer to power off 9.891
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.964
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.552
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.360
When the network is plugged 0.078
And Tor is ready 21.150
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.029
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.956
Given I shutdown Tails and wait for the computer to power off 4.783
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.152
Then Tails is running version 6.3~testoverlayfs 0.137
And all tps features are active 3.923
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.084
And Tor is ready 48.169
Then the Upgrader considers the system as up-to-date 0.336
# 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 17.363
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.477
After features/support/hooks.rb:330 0.771
After features/support/hooks.rb:100 0.014
42.815
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.236
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.486
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.279
And the signing key used by the Upgrader is outdated 0.183
But a current signing key is available on our website 0.000
When the network is plugged 0.109
And Tor is ready 23.499
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.019
After features/support/hooks.rb:330 0.692
After features/support/hooks.rb:100 0.000