Project Number Date
test_Tails_ISO_devel 4521 30 Jul 2026, 00:29

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:52.299 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:0.545
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.106
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 13.487
When I start Tails from USB drive "old" with network unplugged 42.302
Then the boot device has safe access rights 2.866
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:339 3.642
After features/support/hooks.rb:108 0.041
Tags: @product
1:29.426
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 54.476
Then Tails is running from USB drive "old" 0.417
And I create a persistent partition 25.102
And I take note of which tps features are available 4.721
Then a Tails persistence partition exists on USB drive "old" 0.569
And I shutdown Tails and wait for the computer to power off 4.088
After features/support/hooks.rb:339 0.457
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.046
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.165
Then Tails is running from USB drive "old" 0.287
And all tps features are active 5.332
When I write some files expected to persist 1.401
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 1.864
And I take note of which tps features are available 3.637
And I shutdown Tails and wait for the computer to power off 4.034
# 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.774
After features/support/hooks.rb:339 0.353
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.347
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 8.067
And I log in to a new session 14.064
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.785
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.096
Then the running Tails is installed on USB drive "to_upgrade" 15.754
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:339 2.188
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.595
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.890
Then all tps features from the old Tails version are active 0.909
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.455
And the expected persistent files created with the old Tails version are present in the filesystem 1.177
And all persistent directories from the old Tails version have safe access rights 1.869
After features/support/hooks.rb:339 0.757
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:59.009
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 with a persistent partition enabled and logged in 8.247
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.333
When the network is plugged 0.013
And Tor is ready 13.973
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.981
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.424
Given I shutdown Tails and wait for the computer to power off 6.761
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.912
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.858
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
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.131
# 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.218
When the network is plugged 0.014
And Tor is ready 10.227
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.351
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.810
Given I shutdown Tails and wait for the computer to power off 4.114
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.696
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 5.364
And the file system changes introduced in version 6.3~testoverlayfs are present 0.377
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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.015
And Tor is ready 10.464
Then the Upgrader considers the system as up-to-date 10.656
# 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.329
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.366
After features/support/hooks.rb:339 1.065
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.328
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.674
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 11.873
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.364
After features/support/hooks.rb:339 0.894
After features/support/hooks.rb:108 0.000