Project Number Date
test_Tails_ISO_devel 4044 30 Oct 2025, 18:24

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 16:33.368 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:0.638
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 27.388
When I start Tails from USB drive "old" with network unplugged 1:27.735
Then the boot device has safe access rights 3.280
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:331 3.639
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.152
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:28.597
Then Tails is running from USB drive "old" 0.413
And I create a persistent partition 30.010
And I take note of which tps features are available 1.359
Then a Tails persistence partition exists on USB drive "old" 0.710
And I shutdown Tails and wait for the computer to power off 4.842
After features/support/hooks.rb:331 0.374
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.549
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:42.367
Then Tails is running from USB drive "old" 0.390
And all tps features are active 2.401
When I write some files expected to persist 1.702
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.300
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 2.472
And I take note of which tps features are available 0.648
And I shutdown Tails and wait for the computer to power off 7.880
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.681
After features/support/hooks.rb:331 0.510
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.954
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 13.311
And I log in to a new session 18.602
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.442
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.083
Then the running Tails is installed on USB drive "to_upgrade" 21.655
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:331 4.053
After features/support/hooks.rb:100 0.000
Tags: @product
1:53.774
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.242
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.845
Then all tps features from the old Tails version are active 1.806
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.527
And the expected persistent files created with the old Tails version are present in the filesystem 1.633
And all persistent directories from the old Tails version have safe access rights 2.411
After features/support/hooks.rb:331 0.710
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:12.494
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 12.395
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
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.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.062
And Tor is ready 15.267
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.850
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.134
Given I shutdown Tails and wait for the computer to power off 11.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.136
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.825
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.252
When the network is plugged 0.081
And Tor is ready 13.272
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.014
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.164
Given I shutdown Tails and wait for the computer to power off 7.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.647
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 2.592
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.184
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.069
And Tor is ready 12.142
Then the Upgrader considers the system as up-to-date 0.252
# 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 6.661
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.738
After features/support/hooks.rb:331 0.986
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
25.804
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 11.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.100
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 12.283
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.865
After features/support/hooks.rb:331 1.126
After features/support/hooks.rb:100 0.000