Project Number Date
test_Tails_ISO_stable 5681 28 May 2025, 13:20

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:58.007 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:48.866
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.542
And I create a 7200 MiB disk named "old" 0.353
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 1:0.567
When I start Tails from USB drive "old" with network unplugged 1:42.104
Then the boot device has safe access rights 3.213
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 7.263
After features/support/hooks.rb:100 0.011
Tags: @product
2:31.232
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.303
And I start Tails from USB drive "old" with network unplugged and I login 1:35.740
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 39.867
And I take note of which tps features are available 5.302
Then a Tails persistence partition exists on USB drive "old" 1.213
And I shutdown Tails and wait for the computer to power off 8.446
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
3:5.631
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 1.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.081
Then Tails is running from USB drive "old" 0.415
And all tps features are active 2.362
When I write some files expected to persist 1.813
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.541
And all persistent directories from the old Tails version have safe access rights 2.750
And I take note of which tps features are available 0.644
And I shutdown Tails and wait for the computer to power off 6.222
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.534
After features/support/hooks.rb:330 0.099
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.232
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 without a persistent partition and stopped at Tails Greeter's login screen 20.365
And I log in to a new session 18.322
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.858
And I plug USB drive "to_upgrade" 2.564
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.484
Then the running Tails is installed on USB drive "to_upgrade" 30.167
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:330 2.300
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.687
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.270
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.952
Then all tps features from the old Tails version are active 2.010
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.663
And the expected persistent files created with the old Tails version are present in the filesystem 1.797
And all persistent directories from the old Tails version have safe access rights 2.616
After features/support/hooks.rb:330 1.568
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:11.684
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 25.883
And no SquashFS delta is installed 0.261
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.415
When the network is plugged 0.069
And Tor is ready 24.119
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.597
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.046
Given I shutdown Tails and wait for the computer to power off 9.277
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.962
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.401
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.358
When the network is plugged 0.101
And Tor is ready 18.597
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.972
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.155
Given I shutdown Tails and wait for the computer to power off 6.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.558
Then Tails is running version 6.3~testoverlayfs 0.051
And all tps features are active 4.075
And the file system changes introduced in version 6.3~testoverlayfs are present 0.565
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.399
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.726
And Tor is ready 15.736
Then the Upgrader considers the system as up-to-date 0.380
# 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 16.696
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.030
After features/support/hooks.rb:330 1.117
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
52.673
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 17.803
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.477
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.479
And Tor is ready 25.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.344
After features/support/hooks.rb:330 0.895
After features/support/hooks.rb:100 0.000