Project Number Date
test_Tails_ISO_devel 3907 15 Jul 2025, 17:56

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 21:37.728 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:13.618
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 33.825
When I start Tails from USB drive "old" with network unplugged 1:32.899
Then the boot device has safe access rights 4.189
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.536
And I unplug USB drive "old" 0.303
After features/support/hooks.rb:330 3.811
After features/support/hooks.rb:100 0.011
Tags: @product
2:22.713
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 1:35.331
Then Tails is running from USB drive "old" 0.402
And I create a persistent partition 32.985
And I take note of which tps features are available 2.290
Then a Tails persistence partition exists on USB drive "old" 0.891
And I shutdown Tails and wait for the computer to power off 10.581
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.010
Tags: @product
3:14.724
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.010
Then Tails is running from USB drive "old" 0.422
And all tps features are active 2.562
When I write some files expected to persist 1.789
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.754
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 7.288
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 21.520
After features/support/hooks.rb:330 0.198
After features/support/hooks.rb:100 0.017
Tags: @product
3:0.040
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.641
And I log in to a new session 19.995
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.254
And I plug USB drive "to_upgrade" 3.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.884
Then the running Tails is installed on USB drive "to_upgrade" 32.629
And I unplug USB drive "to_upgrade" 1.853
And I unplug USB drive "__internal" 0.531
After features/support/hooks.rb:330 1.099
After features/support/hooks.rb:100 0.000
Tags: @product
2:45.425
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.327
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:33.597
Then all tps features from the old Tails version are active 2.368
And Tails is running from USB drive "to_upgrade" 0.519
And the boot device has safe access rights 4.050
And the expected persistent files created with the old Tails version are present in the filesystem 1.880
And all persistent directories from the old Tails version have safe access rights 2.682
After features/support/hooks.rb:330 1.921
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:15.531
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.484
And no SquashFS delta is installed 0.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.455
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.555
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.539
When the network is plugged 0.072
And Tor is ready 21.751
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.305
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.415
Given I shutdown Tails and wait for the computer to power off 8.025
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.602
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.822
And the file system changes introduced in version 6.2~testoverlayfs are present 0.455
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.378
# 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.371
When the network is plugged 0.084
And Tor is ready 19.152
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.988
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.230
Given I shutdown Tails and wait for the computer to power off 6.772
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.392
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 3.060
And the file system changes introduced in version 6.3~testoverlayfs are present 0.564
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.433
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.333
When the network is plugged 0.115
And Tor is ready 19.595
Then the Upgrader considers the system as up-to-date 0.515
# 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.793
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.810
After features/support/hooks.rb:330 0.797
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
45.674
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 11.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.865
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.198
But a current signing key is available on our website 0.000
When the network is plugged 0.191
And Tor is ready 24.915
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.302
After features/support/hooks.rb:330 0.840
After features/support/hooks.rb:100 0.000