Project Number Date
test_Tails_ISO_devel 4329 08 Apr 2026, 14:51

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 12:26.323 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:9.350
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.304
When I start Tails from USB drive "old" with network unplugged 51.614
Then the boot device has safe access rights 2.578
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:331 1.208
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.040
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 52.243
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 24.242
And I take note of which tps features are available 0.667
Then a Tails persistence partition exists on USB drive "old" 0.567
And I shutdown Tails and wait for the computer to power off 8.029
After features/support/hooks.rb:331 0.348
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.377
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.833
Then Tails is running from USB drive "old" 0.262
And all tps features are active 1.166
When I write some files expected to persist 1.206
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.451
And all persistent directories from the old Tails version have safe access rights 1.828
And I take note of which tps features are available 0.154
And I shutdown Tails and wait for the computer to power off 7.807
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.456
After features/support/hooks.rb:331 0.446
After features/support/hooks.rb:100 0.006
Tags: @product
2:15.632
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.531
And I log in to a new session 17.152
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.781
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.038
Then the running Tails is installed on USB drive "to_upgrade" 15.598
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 3.690
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.542
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.882
Then all tps features from the old Tails version are active 1.055
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.268
And the expected persistent files created with the old Tails version are present in the filesystem 1.074
And all persistent directories from the old Tails version have safe access rights 1.966
After features/support/hooks.rb:331 0.698
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:33.333
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.173
And no SquashFS delta is installed 0.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.360
When the network is plugged 0.015
And Tor is ready 22.474
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.350
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.323
Given I shutdown Tails and wait for the computer to power off 20.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.210
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.232
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
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.156
# 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.184
When the network is plugged 0.020
And Tor is ready 20.445
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.362
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.913
Given I shutdown Tails and wait for the computer to power off 7.902
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.765
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.136
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.016
And Tor is ready 22.348
Then the Upgrader considers the system as up-to-date 0.099
# 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 4.093
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.379
After features/support/hooks.rb:331 0.640
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
26.047
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.653
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 17.590
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.388
After features/support/hooks.rb:331 0.712
After features/support/hooks.rb:100 0.000