Project Number Date
test_Tails_ISO_stable 5630 07 May 2025, 09:39

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 18:34.043 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
1:56.066
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.406
When I start Tails from USB drive "old" with network unplugged 1:18.747
Then the boot device has safe access rights 2.743
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:330 3.514
After features/support/hooks.rb:100 0.019
Tags: @product
2:3.459
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:21.923
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 30.624
And I take note of which tps features are available 1.546
Then a Tails persistence partition exists on USB drive "old" 0.701
And I shutdown Tails and wait for the computer to power off 8.173
After features/support/hooks.rb:330 0.184
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.797
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.858
Then Tails is running from USB drive "old" 0.304
And all tps features are active 2.086
When I write some files expected to persist 1.595
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.570
And I take note of which tps features are available 0.522
And I shutdown Tails and wait for the computer to power off 4.283
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.785
After features/support/hooks.rb:330 0.123
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.984
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 10.023
And I log in to a new session 18.061
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.456
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.074
Then the running Tails is installed on USB drive "to_upgrade" 18.526
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 2.163
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.840
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.249
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.363
Then all tps features from the old Tails version are active 1.627
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.263
And the expected persistent files created with the old Tails version are present in the filesystem 1.586
And all persistent directories from the old Tails version have safe access rights 2.385
After features/support/hooks.rb:330 1.277
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:32.016
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 10.793
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.401
When the network is plugged 0.068
And Tor is ready 17.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.951
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.195
Given I shutdown Tails and wait for the computer to power off 10.892
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.375
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.998
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.304
When the network is plugged 0.076
And Tor is ready 19.634
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.320
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.475
Given I shutdown Tails and wait for the computer to power off 4.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.719
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.025
And the file system changes introduced in version 6.3~testoverlayfs are present 0.447
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.092
And Tor is ready 17.101
Then the Upgrader considers the system as up-to-date 10.845
# 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.460
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.311
After features/support/hooks.rb:330 0.699
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
37.877
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 9.946
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the signing key used by the Upgrader is outdated 0.121
But a current signing key is available on our website 0.000
When the network is plugged 0.111
And Tor is ready 17.956
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.215
After features/support/hooks.rb:330 0.633
After features/support/hooks.rb:100 0.000