Project Number Date
test_Tails_ISO_devel 4511 24 Jul 2026, 11:23

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:5.717 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:15.067
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.849
When I start Tails from USB drive "old" with network unplugged 56.526
Then the boot device has safe access rights 2.942
And Tails is running from USB drive "old" 0.216
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.409
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.755
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 54.989
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 24.442
And I take note of which tps features are available 5.643
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 4.692
After features/support/hooks.rb:339 0.206
After features/support/hooks.rb:108 0.007
Tags: @product
1:37.718
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.121
Then Tails is running from USB drive "old" 0.221
And all tps features are active 4.539
When I write some files expected to persist 1.332
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.156
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.176
And I take note of which tps features are available 4.228
And I shutdown Tails and wait for the computer to power off 4.175
# 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" 12.329
After features/support/hooks.rb:339 0.141
After features/support/hooks.rb:108 0.008
Tags: @product
2:12.654
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.026
And I log in to a new session 12.710
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.827
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.064
Then the running Tails is installed on USB drive "to_upgrade" 16.456
And I unplug USB drive "to_upgrade" 0.177
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 0.870
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.207
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.660
Then all tps features from the old Tails version are active 1.138
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.593
And the expected persistent files created with the old Tails version are present in the filesystem 1.279
And all persistent directories from the old Tails version have safe access rights 2.184
After features/support/hooks.rb:339 0.612
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:53.091
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.824
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.020
And Tor is ready 13.941
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.922
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.152
Given I shutdown Tails and wait for the computer to power off 7.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.813
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 5.784
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.183
# 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.190
When the network is plugged 0.020
And Tor is ready 10.552
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.104
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.802
Given I shutdown Tails and wait for the computer to power off 4.172
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.798
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.708
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.017
And Tor is ready 11.109
Then the Upgrader considers the system as up-to-date 10.549
# 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.745
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.422
After features/support/hooks.rb:339 0.786
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.222
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.491
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 11.508
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.861
After features/support/hooks.rb:339 1.128
After features/support/hooks.rb:108 0.000