Project Number Date
test_Tails_ISO_stable 6025 28 Dec 2025, 11:50

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 13:24.252 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.996
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 30.952
When I start Tails from USB drive "old" with network unplugged 1:18.046
Then the boot device has safe access rights 2.911
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:331 4.025
After features/support/hooks.rb:100 0.009
Tags: @product
1:34.639
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:0.820
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 26.817
And I take note of which tps features are available 1.087
Then a Tails persistence partition exists on USB drive "old" 0.642
And I shutdown Tails and wait for the computer to power off 4.760
After features/support/hooks.rb:331 0.365
After features/support/hooks.rb:100 0.009
Tags: @product
1:41.327
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.409
Then Tails is running from USB drive "old" 0.300
And all tps features are active 1.803
When I write some files expected to persist 1.510
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.220
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 7.408
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.395
After features/support/hooks.rb:331 0.545
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.122
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 without a persistent partition and stopped at Tails Greeter's login screen 13.134
And I log in to a new session 15.391
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.223
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.051
Then the running Tails is installed on USB drive "to_upgrade" 19.450
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:331 3.838
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.148
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.132
Then all tps features from the old Tails version are active 1.337
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 2.667
And the expected persistent files created with the old Tails version are present in the filesystem 1.323
And all persistent directories from the old Tails version have safe access rights 2.191
After features/support/hooks.rb:331 0.713
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
3:58.240
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 11.276
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.057
And Tor is ready 14.392
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.562
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.309
Given I shutdown Tails and wait for the computer to power off 10.749
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.916
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.877
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
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.166
# 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.234
When the network is plugged 0.069
And Tor is ready 11.335
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.586
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.695
Given I shutdown Tails and wait for the computer to power off 7.636
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.320
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.980
And the file system changes introduced in version 6.3~testoverlayfs are present 0.418
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.173
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.054
And Tor is ready 11.662
Then the Upgrader considers the system as up-to-date 0.131
# 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.372
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.895
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
22.777
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.166
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 10.559
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.672
After features/support/hooks.rb:331 1.079
After features/support/hooks.rb:100 0.000