Project Number Date
test_Tails_ISO_stable 5705 10 Jun 2025, 13:22

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:10.937 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:17.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 35.014
When I start Tails from USB drive "old" with network unplugged 1:37.144
Then the boot device has safe access rights 3.332
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 7.109
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.496
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:28.347
Then Tails is running from USB drive "old" 0.436
And I create a persistent partition 31.972
And I take note of which tps features are available 1.480
Then a Tails persistence partition exists on USB drive "old" 0.758
And I shutdown Tails and wait for the computer to power off 8.310
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.534
Then Tails is running from USB drive "old" 0.417
And all tps features are active 1.985
When I write some files expected to persist 1.737
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.485
And all persistent directories from the old Tails version have safe access rights 2.945
And I take note of which tps features are available 0.385
And I shutdown Tails and wait for the computer to power off 6.521
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.110
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.712
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.962
And I log in to a new session 19.344
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.972
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.405
Then the running Tails is installed on USB drive "to_upgrade" 29.208
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 2.386
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.589
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.221
Then all tps features from the old Tails version are active 1.831
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.817
And the expected persistent files created with the old Tails version are present in the filesystem 1.519
And all persistent directories from the old Tails version have safe access rights 2.681
After features/support/hooks.rb:330 1.148
After features/support/hooks.rb:100 0.007
7:10.629
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.859
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.119
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.555
When the network is plugged 0.151
And Tor is ready 20.327
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.321
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.764
Given I shutdown Tails and wait for the computer to power off 8.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.143
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.125
And the file system changes introduced in version 6.2~testoverlayfs are present 0.440
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.484
# 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.288
When the network is plugged 0.069
And Tor is ready 46.562
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.564
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.385
Given I shutdown Tails and wait for the computer to power off 4.477
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.220
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.077
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
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.360
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.328
When the network is plugged 0.064
And Tor is ready 18.511
Then the Upgrader considers the system as up-to-date 0.292
# 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.369
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.779
After features/support/hooks.rb:330 0.771
After features/support/hooks.rb:100 0.017
42.209
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.046
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 23.167
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.399
After features/support/hooks.rb:330 0.838
After features/support/hooks.rb:100 0.000