Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 81 02 Jul 2026, 14:34

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:40.250 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:8.032
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 12.901
When I start Tails from USB drive "old" with network unplugged 50.662
Then the boot device has safe access rights 2.703
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.389
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.720
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 52.940
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 24.163
And I take note of which tps features are available 3.825
Then a Tails persistence partition exists on USB drive "old" 0.522
And I shutdown Tails and wait for the computer to power off 7.951
After features/support/hooks.rb:339 0.148
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.148
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.228
Then Tails is running from USB drive "old" 0.219
And all tps features are active 4.788
When I write some files expected to persist 1.226
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 1.727
And I take note of which tps features are available 3.708
And I shutdown Tails and wait for the computer to power off 7.988
# 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.756
After features/support/hooks.rb:339 0.197
After features/support/hooks.rb:108 0.007
Tags: @product
2:9.004
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 7.732
And I log in to a new session 12.507
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.655
And I plug USB drive "to_upgrade" 2.355
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.143
Then the running Tails is installed on USB drive "to_upgrade" 14.329
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:339 2.087
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.442
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.860
Then all tps features from the old Tails version are active 1.001
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.344
And the expected persistent files created with the old Tails version are present in the filesystem 1.076
And all persistent directories from the old Tails version have safe access rights 1.871
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:50.522
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.854
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
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.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.018
And Tor is ready 13.559
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.558
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.609
Given I shutdown Tails and wait for the computer to power off 9.278
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.435
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.847
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.227
When the network is plugged 0.015
And Tor is ready 10.386
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.202
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.164
Given I shutdown Tails and wait for the computer to power off 7.915
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.865
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.891
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.017
And Tor is ready 10.869
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 3.783
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:339 0.903
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.380
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.224
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
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.019
And Tor is ready 11.113
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.733
After features/support/hooks.rb:339 0.848
After features/support/hooks.rb:108 0.000