Project Number Date
test_Tails_ISO_devel 4423 31 May 2026, 11:05

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:0.944 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:1.978
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.096
When I start Tails from USB drive "old" with network unplugged 44.383
Then the boot device has safe access rights 2.659
And Tails is running from USB drive "old" 0.275
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.161
After features/support/hooks.rb:335 3.604
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.620
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 52.148
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 24.152
And I take note of which tps features are available 0.341
Then a Tails persistence partition exists on USB drive "old" 0.521
And I shutdown Tails and wait for the computer to power off 8.151
After features/support/hooks.rb:335 0.285
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.825
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.969
Then Tails is running from USB drive "old" 0.281
And all tps features are active 1.177
When I write some files expected to persist 1.199
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.264
And all persistent directories from the old Tails version have safe access rights 1.800
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 7.872
# 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.889
After features/support/hooks.rb:335 0.464
After features/support/hooks.rb:104 0.006
Tags: @product
2:7.609
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.746
And I log in to a new session 11.357
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.814
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.231
Then the running Tails is installed on USB drive "to_upgrade" 13.942
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 2.124
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.557
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.774
Then all tps features from the old Tails version are active 0.999
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.400
And the expected persistent files created with the old Tails version are present in the filesystem 1.173
And all persistent directories from the old Tails version have safe access rights 1.900
After features/support/hooks.rb:335 0.672
After features/support/hooks.rb:104 0.006
3:32.262
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.913
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.304
When the network is plugged 0.017
And Tor is ready 13.356
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.658
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.654
Given I shutdown Tails and wait for the computer to power off 10.786
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.989
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.107
And the file system changes introduced in version 6.2~testoverlayfs are present 0.194
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.176
When the network is plugged 0.013
And Tor is ready 9.828
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.073
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.197
Given I shutdown Tails and wait for the computer to power off 7.922
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.567
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.099
And the file system changes introduced in version 6.3~testoverlayfs are present 0.318
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.016
And Tor is ready 9.814
Then the Upgrader considers the system as up-to-date 10.552
# 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.217
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.362
After features/support/hooks.rb:335 0.770
After features/support/hooks.rb:104 0.010
20.090
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.443
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.791
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.524
After features/support/hooks.rb:335 0.643
After features/support/hooks.rb:104 0.000