Project Number Date
test_Tails_ISO_devel 3873 18 Jun 2025, 07:16

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:54.665 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:19.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 35.105
When I start Tails from USB drive "old" with network unplugged 1:37.966
Then the boot device has safe access rights 3.652
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 3.789
After features/support/hooks.rb:100 0.011
Tags: @product
2:22.266
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:35.484
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 34.739
And I take note of which tps features are available 1.807
Then a Tails persistence partition exists on USB drive "old" 1.047
And I shutdown Tails and wait for the computer to power off 8.597
After features/support/hooks.rb:330 0.214
After features/support/hooks.rb:100 0.011
Tags: @product
3:5.632
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.743
Then Tails is running from USB drive "old" 0.623
And all tps features are active 2.836
When I write some files expected to persist 1.807
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.315
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 3.394
And I take note of which tps features are available 0.509
And I shutdown Tails and wait for the computer to power off 6.466
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.224
After features/support/hooks.rb:330 0.360
After features/support/hooks.rb:100 0.011
Tags: @product
2:42.715
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.060
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.753
And I log in to a new session 20.898
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.366
And I plug USB drive "to_upgrade" 2.507
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.346
Then the running Tails is installed on USB drive "to_upgrade" 27.371
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.252
After features/support/hooks.rb:330 3.870
After features/support/hooks.rb:100 0.000
Tags: @product
2:34.450
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.688
Then all tps features from the old Tails version are active 2.043
And Tails is running from USB drive "to_upgrade" 0.494
And the boot device has safe access rights 4.133
And the expected persistent files created with the old Tails version are present in the filesystem 2.395
And all persistent directories from the old Tails version have safe access rights 3.469
After features/support/hooks.rb:330 1.589
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
8:9.003
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.608
And no SquashFS delta is installed 0.162
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.461
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.188
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.593
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.676
When the network is plugged 0.082
And Tor is ready 50.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.770
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.423
Given I shutdown Tails and wait for the computer to power off 11.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.956
Then Tails is running version 6.2~testoverlayfs 0.131
And all tps features are active 2.206
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.459
# 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.488
When the network is plugged 0.099
And Tor is ready 20.257
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.742
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.476
Given I shutdown Tails and wait for the computer to power off 6.759
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.098
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.264
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.500
When the network is plugged 0.080
And Tor is ready 21.023
Then the Upgrader considers the system as up-to-date 0.346
# 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 18.965
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.786
After features/support/hooks.rb:330 0.860
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
41.491
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 11.494
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.124
And the signing key used by the Upgrader is outdated 0.173
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 21.721
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.572
After features/support/hooks.rb:330 0.896
After features/support/hooks.rb:100 0.000