Project Number Date
test_Tails_ISO_devel 4052 04 Nov 2025, 12: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 15:38.591 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:53.293
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 31.345
When I start Tails from USB drive "old" with network unplugged 1:16.584
Then the boot device has safe access rights 3.223
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:331 3.986
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.736
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:24.409
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 29.010
And I take note of which tps features are available 1.395
Then a Tails persistence partition exists on USB drive "old" 0.667
And I shutdown Tails and wait for the computer to power off 7.765
After features/support/hooks.rb:331 0.276
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.000
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:34.844
Then Tails is running from USB drive "old" 0.659
And all tps features are active 1.820
When I write some files expected to persist 1.447
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 2.114
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 8.153
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.794
After features/support/hooks.rb:331 0.457
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.399
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.787
And I log in to a new session 15.830
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.498
And I plug USB drive "to_upgrade" 2.399
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.878
Then the running Tails is installed on USB drive "to_upgrade" 20.597
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:331 4.017
After features/support/hooks.rb:100 0.000
Tags: @product
1:42.667
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:34.450
Then all tps features from the old Tails version are active 1.314
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 2.940
And the expected persistent files created with the old Tails version are present in the filesystem 1.297
And all persistent directories from the old Tails version have safe access rights 2.182
After features/support/hooks.rb:331 1.158
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:53.819
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.278
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.051
And Tor is ready 14.054
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.830
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.230
Given I shutdown Tails and wait for the computer to power off 11.185
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.286
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.347
And the file system changes introduced in version 6.2~testoverlayfs are present 0.253
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.180
# 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.233
When the network is plugged 0.049
And Tor is ready 12.697
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.569
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.925
Given I shutdown Tails and wait for the computer to power off 7.653
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.075
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.013
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.060
And Tor is ready 11.637
Then the Upgrader considers the system as up-to-date 0.234
# 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 5.343
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.432
After features/support/hooks.rb:331 0.878
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
23.674
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 10.036
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.109
And Tor is ready 11.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.741
After features/support/hooks.rb:331 1.032
After features/support/hooks.rb:100 0.000