Project Number Date
test_Tails_ISO_devel 4563 21 Aug 2026, 16:30

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 11:19.873 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:14.642
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.104
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.667
When I start Tails from USB drive "old" with network unplugged 57.085
Then the boot device has safe access rights 2.132
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 1.654
After features/support/hooks.rb:108 0.006
Tags: @product
1:22.645
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 49.295
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 23.700
And I take note of which tps features are available 6.295
Then a Tails persistence partition exists on USB drive "old" 0.489
And I shutdown Tails and wait for the computer to power off 2.540
After features/support/hooks.rb:339 0.202
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.986
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.859
Then Tails is running from USB drive "old" 0.236
And all tps features are active 7.815
When I write some files expected to persist 1.256
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.118
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 1.549
And I take note of which tps features are available 6.593
And I shutdown Tails and wait for the computer to power off 2.544
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.614
After features/support/hooks.rb:339 0.284
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.527
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.094
And I log in to a new session 11.363
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.662
And I plug USB drive "to_upgrade" 2.200
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.280
Then the running Tails is installed on USB drive "to_upgrade" 17.634
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:339 2.001
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.542
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.444
Then all tps features from the old Tails version are active 1.067
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.056
And the expected persistent files created with the old Tails version are present in the filesystem 1.062
And all persistent directories from the old Tails version have safe access rights 1.600
After features/support/hooks.rb:339 0.653
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:30.338
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.924
And no SquashFS delta is installed 0.112
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.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.043
And Tor is ready 12.595
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.054
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.687
Given I shutdown Tails and wait for the computer to power off 5.439
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.654
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.784
And the file system changes introduced in version 6.2~testoverlayfs are present 0.212
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.114
# 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.202
When the network is plugged 0.023
And Tor is ready 10.452
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.579
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.456
Given I shutdown Tails and wait for the computer to power off 2.563
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.569
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.030
And Tor is ready 10.054
Then the Upgrader considers the system as up-to-date 0.086
# 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 3.568
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.322
After features/support/hooks.rb:339 0.967
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.189
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 8.744
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.025
After features/support/hooks.rb:339 0.945
After features/support/hooks.rb:108 0.000