Project Number Date
test_Tails_ISO_stable 5700 06 Jun 2025, 13:06

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:45.088 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:31.550
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.267
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.074
And I write an old version of the Tails USB image to disk "old" 35.204
When I start Tails from USB drive "old" with network unplugged 1:49.680
Then the boot device has safe access rights 4.109
And Tails is running from USB drive "old" 0.407
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.235
After features/support/hooks.rb:330 4.280
After features/support/hooks.rb:100 0.015
Tags: @product
2:31.644
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.331
And I start Tails from USB drive "old" with network unplugged and I login 1:45.014
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 33.013
And I take note of which tps features are available 2.936
Then a Tails persistence partition exists on USB drive "old" 0.905
And I shutdown Tails and wait for the computer to power off 9.075
After features/support/hooks.rb:330 0.221
After features/support/hooks.rb:100 0.020
Tags: @product
3:18.518
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.472
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.238
Then Tails is running from USB drive "old" 0.368
And all tps features are active 3.182
When I write some files expected to persist 2.710
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.280
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.758
And I take note of which tps features are available 0.633
And I shutdown Tails and wait for the computer to power off 6.675
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.770
After features/support/hooks.rb:330 0.174
After features/support/hooks.rb:100 0.011
Tags: @product
3:4.302
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 without a persistent partition and stopped at Tails Greeter's login screen 25.490
And I log in to a new session 22.783
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.035
And I plug USB drive "to_upgrade" 2.597
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.328
Then the running Tails is installed on USB drive "to_upgrade" 30.629
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 2.594
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.749
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.019
Then all tps features from the old Tails version are active 2.042
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.693
And the expected persistent files created with the old Tails version are present in the filesystem 1.665
And all persistent directories from the old Tails version have safe access rights 2.729
After features/support/hooks.rb:330 0.696
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:10.131
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 13.986
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.557
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.625
When the network is plugged 0.075
And Tor is ready 22.183
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.234
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.838
Given I shutdown Tails and wait for the computer to power off 11.970
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.827
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.307
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.452
# 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.303
When the network is plugged 0.078
And Tor is ready 19.171
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.676
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.461
Given I shutdown Tails and wait for the computer to power off 4.553
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.200
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.184
And the file system changes introduced in version 6.3~testoverlayfs are present 0.540
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.448
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.085
And Tor is ready 20.044
Then the Upgrader considers the system as up-to-date 0.333
# 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.690
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.970
After features/support/hooks.rb:330 0.898
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
43.192
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 10.719
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.493
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.134
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 22.860
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.801
After features/support/hooks.rb:330 0.945
After features/support/hooks.rb:100 0.000