Project Number Date
test_Tails_ISO_stable 5938 08 Nov 2025, 12:05

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:54.809 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:2.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 6.243
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 31.379
When I start Tails from USB drive "old" with network unplugged 1:19.727
Then the boot device has safe access rights 2.796
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:331 3.866
After features/support/hooks.rb:100 0.025
Tags: @product
2:7.418
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:26.419
Then Tails is running from USB drive "old" 0.632
And I create a persistent partition 29.730
And I take note of which tps features are available 1.729
Then a Tails persistence partition exists on USB drive "old" 0.828
And I shutdown Tails and wait for the computer to power off 7.867
After features/support/hooks.rb:331 0.595
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.909
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.560
Then Tails is running from USB drive "old" 0.645
And all tps features are active 1.904
When I write some files expected to persist 1.734
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.211
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 7.576
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.033
After features/support/hooks.rb:331 0.516
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.411
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.807
And I log in to a new session 16.981
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.481
And I plug USB drive "to_upgrade" 2.552
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.050
Then the running Tails is installed on USB drive "to_upgrade" 21.102
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:331 4.095
After features/support/hooks.rb:100 0.000
Tags: @product
1:48.420
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.158
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:39.532
Then all tps features from the old Tails version are active 1.499
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.315
And the expected persistent files created with the old Tails version are present in the filesystem 1.277
And all persistent directories from the old Tails version have safe access rights 2.330
After features/support/hooks.rb:331 0.948
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:50.200
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.508
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.353
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.602
When the network is plugged 0.083
And Tor is ready 14.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.705
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.669
Given I shutdown Tails and wait for the computer to power off 8.288
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.619
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.035
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.179
# 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.227
When the network is plugged 0.051
And Tor is ready 12.932
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.582
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.552
Given I shutdown Tails and wait for the computer to power off 7.503
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:35.404
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.030
And the file system changes introduced in version 6.3~testoverlayfs are present 0.425
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.055
And Tor is ready 12.197
Then the Upgrader considers the system as up-to-date 0.207
# 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.104
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.558
After features/support/hooks.rb:331 0.953
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
23.368
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.460
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
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.058
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 11.576
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.846
After features/support/hooks.rb:331 0.979
After features/support/hooks.rb:100 0.000