Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 66 18 Jun 2026, 14:37

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:50.539 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:2.270
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.122
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 12.941
When I start Tails from USB drive "old" with network unplugged 44.901
Then the boot device has safe access rights 2.594
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.285
After features/support/hooks.rb:108 0.015
Tags: @product
1:29.692
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 53.333
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 24.538
And I take note of which tps features are available 4.088
Then a Tails persistence partition exists on USB drive "old" 0.552
And I shutdown Tails and wait for the computer to power off 6.755
After features/support/hooks.rb:339 0.178
After features/support/hooks.rb:108 0.015
Tags: @product
1:36.977
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.538
Then Tails is running from USB drive "old" 0.268
And all tps features are active 5.257
When I write some files expected to persist 1.252
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.309
And all persistent directories from the old Tails version have safe access rights 2.017
And I take note of which tps features are available 3.871
And I shutdown Tails and wait for the computer to power off 8.210
# 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.947
After features/support/hooks.rb:339 0.388
After features/support/hooks.rb:108 0.016
Tags: @product
2:9.068
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.636
And I log in to a new session 11.495
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.750
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.708
Then the running Tails is installed on USB drive "to_upgrade" 14.930
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 3.044
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.543
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.577
Then all tps features from the old Tails version are active 0.948
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.495
And the expected persistent files created with the old Tails version are present in the filesystem 1.123
And all persistent directories from the old Tails version have safe access rights 1.951
After features/support/hooks.rb:339 0.689
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
3:59.481
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.574
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.317
When the network is plugged 0.024
And Tor is ready 13.825
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.780
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.251
Given I shutdown Tails and wait for the computer to power off 9.557
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.892
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.959
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.200
When the network is plugged 0.016
And Tor is ready 10.836
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.124
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.768
Given I shutdown Tails and wait for the computer to power off 8.138
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.601
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.260
And the file system changes introduced in version 6.3~testoverlayfs are present 0.339
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.015
And Tor is ready 10.362
Then the Upgrader considers the system as up-to-date 10.581
# 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.256
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:339 0.956
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
20.505
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.600
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.041
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.016
And Tor is ready 9.932
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.641
After features/support/hooks.rb:339 0.778
After features/support/hooks.rb:108 0.000