Project Number Date
test_Tails_ISO_stable 5718 17 Jun 2025, 15:01

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 27:58.626 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
3:4.749
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.119
And I write an old version of the Tails USB image to disk "old" 43.349
When I start Tails from USB drive "old" with network unplugged 2:15.139
Then the boot device has safe access rights 3.674
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.187
And udev-watchdog is monitoring the correct device 0.388
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:330 8.693
After features/support/hooks.rb:100 0.128
Tags: @product
3:1.262
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.054
Given a computer 1.304
And I start Tails from USB drive "old" with network unplugged and I login 1:57.326
Then Tails is running from USB drive "old" 1.137
And I create a persistent partition 46.130
And I take note of which tps features are available 2.378
Then a Tails persistence partition exists on USB drive "old" 1.217
And I shutdown Tails and wait for the computer to power off 11.767
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.012
Tags: @product
4:25.537
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.394
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:25.177
Then Tails is running from USB drive "old" 0.893
And all tps features are active 2.533
When I write some files expected to persist 3.343
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 2.211
And all persistence configuration files have safe access rights 1.407
And all persistent directories from the old Tails version have safe access rights 6.137
And I take note of which tps features are available 0.776
And I shutdown Tails and wait for the computer to power off 6.639
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 36.022
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.012
Tags: @product
3:40.344
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 25.326
And I log in to a new session 34.058
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.179
And I plug USB drive "to_upgrade" 2.595
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.964
Then the running Tails is installed on USB drive "to_upgrade" 43.743
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 5.515
After features/support/hooks.rb:100 0.000
Tags: @product
3:17.109
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.178
Given a computer 1.774
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:57.330
Then all tps features from the old Tails version are active 6.555
And Tails is running from USB drive "to_upgrade" 0.624
And the boot device has safe access rights 5.813
And the expected persistent files created with the old Tails version are present in the filesystem 1.683
And all persistent directories from the old Tails version have safe access rights 3.327
After features/support/hooks.rb:330 2.018
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
9:34.284
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.915
And no SquashFS delta is installed 1.576
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.825
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.395
When the network is plugged 0.200
And Tor is ready 25.631
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 15.273
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 23.055
Given I shutdown Tails and wait for the computer to power off 14.590
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:3.623
Then Tails is running version 6.2~testoverlayfs 0.033
And all tps features are active 2.807
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.446
# 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.311
When the network is plugged 0.070
And Tor is ready 35.236
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.805
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.798
Given I shutdown Tails and wait for the computer to power off 6.802
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:41.181
Then Tails is running version 6.3~testoverlayfs 0.032
And all tps features are active 2.559
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.483
When the network is plugged 0.351
And Tor is ready 25.037
Then the Upgrader considers the system as up-to-date 1.028
# 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 25.134
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.294
After features/support/hooks.rb:330 0.761
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
55.337
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 16.012
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 28.212
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.523
After features/support/hooks.rb:330 1.234
After features/support/hooks.rb:100 0.000