Project Number Date
test_Tails_ISO_stable 5708 10 Jun 2025, 19:38

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 19:52.443 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
2:10.649
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.286
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 31.981
When I start Tails from USB drive "old" with network unplugged 1:32.942
Then the boot device has safe access rights 3.201
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.373
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 3.547
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.347
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:34.959
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 31.462
And I take note of which tps features are available 2.062
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 6.448
After features/support/hooks.rb:330 0.185
After features/support/hooks.rb:100 0.011
Tags: @product
2:53.050
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.440
Then Tails is running from USB drive "old" 0.364
And all tps features are active 2.079
When I write some files expected to persist 1.811
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.607
And I take note of which tps features are available 0.666
And I shutdown Tails and wait for the computer to power off 4.542
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.760
After features/support/hooks.rb:330 0.138
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.505
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.354
And I log in to a new session 19.588
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.987
And I plug USB drive "to_upgrade" 2.392
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.966
Then the running Tails is installed on USB drive "to_upgrade" 25.761
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:330 3.677
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.473
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.561
Then all tps features from the old Tails version are active 1.575
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.204
And the expected persistent files created with the old Tails version are present in the filesystem 1.516
And all persistent directories from the old Tails version have safe access rights 2.528
After features/support/hooks.rb:330 1.496
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:36.246
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.258
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.101
And Tor is ready 21.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.083
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.878
Given I shutdown Tails and wait for the computer to power off 8.646
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.296
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.289
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.286
# 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.296
When the network is plugged 0.069
And Tor is ready 19.233
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.991
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.109
Given I shutdown Tails and wait for the computer to power off 4.299
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.673
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.969
And the file system changes introduced in version 6.3~testoverlayfs are present 0.716
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.319
When the network is plugged 0.069
And Tor is ready 19.875
Then the Upgrader considers the system as up-to-date 0.339
# 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 14.907
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.717
After features/support/hooks.rb:330 0.719
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
59.454
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.912
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 48.417
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.587
After features/support/hooks.rb:330 0.822
After features/support/hooks.rb:100 0.000