Project Number Date
test_Tails_ISO_devel 4066 11 Nov 2025, 14:20

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:20.571 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.392
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 36.305
When I start Tails from USB drive "old" with network unplugged 1:19.052
Then the boot device has safe access rights 2.862
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.239
After features/support/hooks.rb:331 3.983
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.307
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:28.464
Then Tails is running from USB drive "old" 0.636
And I create a persistent partition 29.332
And I take note of which tps features are available 1.255
Then a Tails persistence partition exists on USB drive "old" 0.669
And I shutdown Tails and wait for the computer to power off 7.751
After features/support/hooks.rb:331 0.730
After features/support/hooks.rb:100 0.012
Tags: @product
2:9.982
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.294
Then Tails is running from USB drive "old" 0.344
And all tps features are active 1.967
When I write some files expected to persist 1.609
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.291
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.446
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 8.063
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.935
After features/support/hooks.rb:331 0.414
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.542
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 13.064
And I log in to a new session 19.551
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.444
And I plug USB drive "to_upgrade" 2.472
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.889
Then the running Tails is installed on USB drive "to_upgrade" 20.635
And I unplug USB drive "to_upgrade" 0.255
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:331 4.014
After features/support/hooks.rb:100 0.000
Tags: @product
1:46.333
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:36.796
Then all tps features from the old Tails version are active 1.836
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.149
And the expected persistent files created with the old Tails version are present in the filesystem 1.311
And all persistent directories from the old Tails version have safe access rights 2.735
After features/support/hooks.rb:331 3.310
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
5:12.279
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.111
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
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.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.527
When the network is plugged 0.131
And Tor is ready 14.603
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.963
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.875
Given I shutdown Tails and wait for the computer to power off 10.979
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.434
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.581
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.187
# 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.291
When the network is plugged 0.062
And Tor is ready 12.055
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.865
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.823
Given I shutdown Tails and wait for the computer to power off 7.886
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.782
Then Tails is running version 6.3~testoverlayfs 0.032
And all tps features are active 2.143
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.840
And Tor is ready 11.946
Then the Upgrader considers the system as up-to-date 0.269
# 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.320
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.487
After features/support/hooks.rb:331 0.966
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
24.733
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.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 11.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.727
After features/support/hooks.rb:331 1.167
After features/support/hooks.rb:100 0.000