Project Number Date
test_Tails_ISO_stable 6529 24 Jul 2026, 11:36

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:28.531 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:7.534
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.047
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.394
When I start Tails from USB drive "old" with network unplugged 49.673
Then the boot device has safe access rights 2.722
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:339 3.572
After features/support/hooks.rb:108 0.007
Tags: @product
1:25.510
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 53.052
Then Tails is running from USB drive "old" 0.217
And I create a persistent partition 23.654
And I take note of which tps features are available 3.932
Then a Tails persistence partition exists on USB drive "old" 0.547
And I shutdown Tails and wait for the computer to power off 4.043
After features/support/hooks.rb:339 0.367
After features/support/hooks.rb:108 0.007
Tags: @product
1:32.417
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.305
Then Tails is running from USB drive "old" 0.250
And all tps features are active 4.813
When I write some files expected to persist 1.337
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 1.871
And I take note of which tps features are available 3.689
And I shutdown Tails and wait for the computer to power off 4.037
# 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.439
After features/support/hooks.rb:339 0.414
After features/support/hooks.rb:108 0.007
Tags: @product
2:8.782
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 without a persistent partition and stopped at Tails Greeter's login screen 7.414
And I log in to a new session 11.674
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.614
And I plug USB drive "to_upgrade" 2.191
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.299
Then the running Tails is installed on USB drive "to_upgrade" 15.318
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:339 2.272
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.809
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.336
Then all tps features from the old Tails version are active 1.003
And Tails is running from USB drive "to_upgrade" 0.211
And the boot device has safe access rights 2.333
And the expected persistent files created with the old Tails version are present in the filesystem 1.081
And all persistent directories from the old Tails version have safe access rights 1.792
After features/support/hooks.rb:339 0.950
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
3:42.599
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.033
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.338
When the network is plugged 0.014
And Tor is ready 13.222
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.154
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.896
Given I shutdown Tails and wait for the computer to power off 5.518
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.123
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.523
And the file system changes introduced in version 6.2~testoverlayfs are present 0.244
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.132
# 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.197
When the network is plugged 0.015
And Tor is ready 10.743
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.690
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.113
Given I shutdown Tails and wait for the computer to power off 4.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.311
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.209
And the file system changes introduced in version 6.3~testoverlayfs are present 0.361
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.012
And Tor is ready 10.189
Then the Upgrader considers the system as up-to-date 10.540
# 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.246
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.428
After features/support/hooks.rb:339 0.962
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
20.877
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.223
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 9.984
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.303
After features/support/hooks.rb:339 0.890
After features/support/hooks.rb:108 0.000