Project Number Date
test_Tails_ISO_stable 6533 27 Jul 2026, 13:33

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:32.684 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:13.950
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.300
When I start Tails from USB drive "old" with network unplugged 54.734
Then the boot device has safe access rights 3.057
And Tails is running from USB drive "old" 0.270
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:339 3.708
After features/support/hooks.rb:108 0.021
Tags: @product
1:35.396
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 56.432
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 28.833
And I take note of which tps features are available 4.963
Then a Tails persistence partition exists on USB drive "old" 0.566
And I shutdown Tails and wait for the computer to power off 4.258
After features/support/hooks.rb:339 0.513
After features/support/hooks.rb:108 0.008
Tags: @product
1:40.215
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.098
Then Tails is running from USB drive "old" 0.328
And all tps features are active 5.549
When I write some files expected to persist 1.283
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.314
And all persistent directories from the old Tails version have safe access rights 2.133
And I take note of which tps features are available 4.487
And I shutdown Tails and wait for the computer to power off 4.155
# 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.616
After features/support/hooks.rb:339 0.161
After features/support/hooks.rb:108 0.015
Tags: @product
2:15.113
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.763
And I log in to a new session 13.123
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.313
And I plug USB drive "to_upgrade" 2.263
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.337
Then the running Tails is installed on USB drive "to_upgrade" 17.037
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 2.549
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.839
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.209
Then all tps features from the old Tails version are active 1.150
And Tails is running from USB drive "to_upgrade" 0.211
And the boot device has safe access rights 2.813
And the expected persistent files created with the old Tails version are present in the filesystem 1.269
And all persistent directories from the old Tails version have safe access rights 2.112
After features/support/hooks.rb:339 1.006
After features/support/hooks.rb:108 0.072
Tags: @product @automatic_upgrade
4:8.149
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.487
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.421
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.224
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.023
And Tor is ready 12.730
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.863
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.714
Given I shutdown Tails and wait for the computer to power off 7.037
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.222
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.296
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.161
# 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.250
When the network is plugged 0.019
And Tor is ready 10.435
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.776
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.965
Given I shutdown Tails and wait for the computer to power off 4.132
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.652
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.478
And the file system changes introduced in version 6.3~testoverlayfs are present 0.414
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.200
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.024
And Tor is ready 12.421
Then the Upgrader considers the system as up-to-date 10.593
# 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.923
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.471
After features/support/hooks.rb:339 0.834
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
21.019
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.750
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.092
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.520
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.285
After features/support/hooks.rb:339 0.786
After features/support/hooks.rb:108 0.000