Project Number Date
test_Tails_ISO_devel 4599 07 Sep 2026, 11:09

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:20.440 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:4.056
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.061
When I start Tails from USB drive "old" with network unplugged 47.627
Then the boot device has safe access rights 1.739
And Tails is running from USB drive "old" 0.144
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.153
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.681
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.293
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 47.132
Then Tails is running from USB drive "old" 0.180
And I create a persistent partition 23.525
And I take note of which tps features are available 6.816
Then a Tails persistence partition exists on USB drive "old" 0.475
And I shutdown Tails and wait for the computer to power off 4.086
After features/support/hooks.rb:339 0.531
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.276
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.516
Then Tails is running from USB drive "old" 0.223
And all tps features are active 7.345
When I write some files expected to persist 1.330
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.247
And all persistent directories from the old Tails version have safe access rights 1.862
And I take note of which tps features are available 6.335
And I shutdown Tails and wait for the computer to power off 2.555
# 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.580
After features/support/hooks.rb:339 0.534
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.946
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.038
And I log in to a new session 12.585
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.751
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.900
Then the running Tails is installed on USB drive "to_upgrade" 18.198
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 1.676
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.184
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.116
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.758
Then all tps features from the old Tails version are active 1.401
And Tails is running from USB drive "to_upgrade" 0.211
And the boot device has safe access rights 2.179
And the expected persistent files created with the old Tails version are present in the filesystem 0.871
And all persistent directories from the old Tails version have safe access rights 1.646
After features/support/hooks.rb:339 0.470
After features/support/hooks.rb:108 0.029
Tags: @product @automatic_upgrade
3:40.671
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.556
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
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.332
When the network is plugged 0.025
And Tor is ready 13.359
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.946
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.734
Given I shutdown Tails and wait for the computer to power off 5.256
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.594
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 7.341
And the file system changes introduced in version 6.2~testoverlayfs are present 0.177
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.111
# 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.174
When the network is plugged 0.029
And Tor is ready 10.448
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.941
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.977
Given I shutdown Tails and wait for the computer to power off 2.591
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.283
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.607
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.093
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.039
And Tor is ready 10.357
Then the Upgrader considers the system as up-to-date 10.411
# 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.758
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.819
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.011
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.896
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 10.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.498
After features/support/hooks.rb:339 0.710
After features/support/hooks.rb:108 0.000