Project Number Date
test_Tails_ISO_devel 4098 03 Dec 2025, 16:09

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.011 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.552
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 34.153
When I start Tails from USB drive "old" with network unplugged 1:20.546
Then the boot device has safe access rights 3.705
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.253
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:331 3.858
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.459
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:29.214
Then Tails is running from USB drive "old" 0.645
And I create a persistent partition 32.790
And I take note of which tps features are available 1.512
Then a Tails persistence partition exists on USB drive "old" 1.141
And I shutdown Tails and wait for the computer to power off 7.971
After features/support/hooks.rb:331 0.656
After features/support/hooks.rb:100 0.010
Tags: @product
2:18.273
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:41.357
Then Tails is running from USB drive "old" 0.310
And all tps features are active 1.929
When I write some files expected to persist 1.747
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.760
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 8.992
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.857
After features/support/hooks.rb:331 0.202
After features/support/hooks.rb:100 0.010
Tags: @product
2:56.599
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.012
And I log in to a new session 17.864
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.429
And I plug USB drive "to_upgrade" 2.384
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.558
Then the running Tails is installed on USB drive "to_upgrade" 23.856
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.263
After features/support/hooks.rb:331 4.043
After features/support/hooks.rb:100 0.000
Tags: @product
1:37.843
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.274
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:27.758
Then all tps features from the old Tails version are active 1.459
And Tails is running from USB drive "to_upgrade" 0.405
And the boot device has safe access rights 3.950
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.467
After features/support/hooks.rb:331 0.699
After features/support/hooks.rb:100 0.009
4:40.470
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 with a persistent partition enabled and logged in 13.117
And no SquashFS delta is installed 0.398
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.538
When the network is plugged 0.057
And Tor is ready 14.580
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.353
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.495
Given I shutdown Tails and wait for the computer to power off 11.813
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:32.000
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.379
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.208
# 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.279
When the network is plugged 0.064
And Tor is ready 13.530
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.148
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.695
Given I shutdown Tails and wait for the computer to power off 8.215
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.913
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.907
And the file system changes introduced in version 6.3~testoverlayfs are present 0.554
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.223
When the network is plugged 0.059
And Tor is ready 12.712
Then the Upgrader considers the system as up-to-date 0.212
# 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.881
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.686
After features/support/hooks.rb:331 0.999
After features/support/hooks.rb:100 0.038
25.812
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.479
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.165
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 11.914
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.756
After features/support/hooks.rb:331 1.161
After features/support/hooks.rb:100 0.000