Project Number Date
test_Tails_ISO_devel 4072 14 Nov 2025, 09:06

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:13.313 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:56.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 30.201
When I start Tails from USB drive "old" with network unplugged 1:21.213
Then the boot device has safe access rights 3.015
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.246
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:331 4.444
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.169
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 1.145
And I start Tails from USB drive "old" with network unplugged and I login 1:23.012
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 28.897
And I take note of which tps features are available 1.081
Then a Tails persistence partition exists on USB drive "old" 0.735
And I shutdown Tails and wait for the computer to power off 7.958
After features/support/hooks.rb:331 0.396
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.099
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.355
Then Tails is running from USB drive "old" 0.386
And all tps features are active 1.897
When I write some files expected to persist 1.724
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.575
And I take note of which tps features are available 0.516
And I shutdown Tails and wait for the computer to power off 7.891
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.918
After features/support/hooks.rb:331 0.316
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.808
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 10.775
And I log in to a new session 16.972
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.170
And I plug USB drive "to_upgrade" 2.575
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.300
Then the running Tails is installed on USB drive "to_upgrade" 20.613
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:331 3.708
After features/support/hooks.rb:100 0.000
Tags: @product
1:45.911
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.301
Then all tps features from the old Tails version are active 1.369
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.017
And the expected persistent files created with the old Tails version are present in the filesystem 1.326
And all persistent directories from the old Tails version have safe access rights 2.385
After features/support/hooks.rb:331 0.997
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:18.568
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 12.567
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.058
And Tor is ready 43.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.600
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.485
Given I shutdown Tails and wait for the computer to power off 12.636
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.154
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.188
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.262
When the network is plugged 0.053
And Tor is ready 12.164
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.821
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.263
Given I shutdown Tails and wait for the computer to power off 3.130
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:35.185
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.155
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.187
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.089
And Tor is ready 12.632
Then the Upgrader considers the system as up-to-date 0.227
# 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.118
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.528
After features/support/hooks.rb:331 1.155
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
25.183
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.561
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 11.372
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.733
After features/support/hooks.rb:331 0.927
After features/support/hooks.rb:100 0.000