Project Number Date
test_Tails_ISO_stable 6019 22 Dec 2025, 11:57

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 14:37.431 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:45.225
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 33.929
When I start Tails from USB drive "old" with network unplugged 1:5.903
Then the boot device has safe access rights 3.196
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:331 3.767
After features/support/hooks.rb:100 0.010
Tags: @product
1:43.197
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:3.971
Then Tails is running from USB drive "old" 0.292
And I create a persistent partition 28.773
And I take note of which tps features are available 1.194
Then a Tails persistence partition exists on USB drive "old" 0.908
And I shutdown Tails and wait for the computer to power off 7.889
After features/support/hooks.rb:331 0.283
After features/support/hooks.rb:100 0.008
Tags: @product
1:47.180
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:14.826
Then Tails is running from USB drive "old" 0.326
And all tps features are active 1.787
When I write some files expected to persist 1.526
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 2.399
And I take note of which tps features are available 2.471
And I shutdown Tails and wait for the computer to power off 4.276
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.685
After features/support/hooks.rb:331 0.229
After features/support/hooks.rb:100 0.021
Tags: @product
2:47.574
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 12.686
And I log in to a new session 15.212
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.587
And I plug USB drive "to_upgrade" 2.813
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.520
Then the running Tails is installed on USB drive "to_upgrade" 19.355
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:331 3.991
After features/support/hooks.rb:100 0.000
Tags: @product
1:25.420
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.474
Then all tps features from the old Tails version are active 1.527
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 4.053
And the expected persistent files created with the old Tails version are present in the filesystem 1.335
And all persistent directories from the old Tails version have safe access rights 2.494
After features/support/hooks.rb:331 3.780
After features/support/hooks.rb:100 0.058
Tags: @product @automatic_upgrade
4:15.276
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 13.219
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
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.258
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.059
And Tor is ready 14.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.800
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.295
Given I shutdown Tails and wait for the computer to power off 11.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.394
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.096
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.250
When the network is plugged 0.054
And Tor is ready 11.684
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.556
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.462
Given I shutdown Tails and wait for the computer to power off 7.892
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.339
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.187
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.055
And Tor is ready 12.755
Then the Upgrader considers the system as up-to-date 0.165
# 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.308
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.489
After features/support/hooks.rb:331 0.851
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
53.556
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.181
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 40.264
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.589
After features/support/hooks.rb:331 0.783
After features/support/hooks.rb:100 0.000