Project Number Date
test_Tails_ISO_stable 5746 28 Jun 2025, 10:22

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 26:49.780 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:44.108
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.093
And I plug USB drive "old" 1.294
And I write an old version of the Tails USB image to disk "old" 42.919
When I start Tails from USB drive "old" with network unplugged 1:54.813
Then the boot device has safe access rights 3.661
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.238
After features/support/hooks.rb:330 12.330
After features/support/hooks.rb:100 0.039
Tags: @product
2:53.182
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given a computer 0.359
And I start Tails from USB drive "old" with network unplugged and I login 1:52.799
Then Tails is running from USB drive "old" 1.295
And I create a persistent partition 46.553
And I take note of which tps features are available 2.615
Then a Tails persistence partition exists on USB drive "old" 1.029
And I shutdown Tails and wait for the computer to power off 8.529
After features/support/hooks.rb:330 0.195
After features/support/hooks.rb:100 0.019
Tags: @product
4:14.160
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.048
Given a computer 2.384
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:12.870
Then Tails is running from USB drive "old" 1.624
And all tps features are active 2.443
When I write some files expected to persist 5.687
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.713
And all persistence configuration files have safe access rights 0.609
And all persistent directories from the old Tails version have safe access rights 3.873
And I take note of which tps features are available 0.515
And I shutdown Tails and wait for the computer to power off 4.757
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 38.679
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.007
Tags: @product
3:41.762
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 without a persistent partition and stopped at Tails Greeter's login screen 25.408
And I log in to a new session 33.868
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.170
And I plug USB drive "to_upgrade" 2.912
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.920
Then the running Tails is installed on USB drive "to_upgrade" 38.969
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.262
After features/support/hooks.rb:330 3.222
After features/support/hooks.rb:100 0.000
Tags: @product
3:16.131
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:59.008
Then all tps features from the old Tails version are active 4.680
And Tails is running from USB drive "to_upgrade" 2.294
And the boot device has safe access rights 5.732
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.737
After features/support/hooks.rb:330 2.047
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
9:12.723
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 with a persistent partition enabled and logged in 17.572
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.635
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.931
When the network is plugged 0.077
And Tor is ready 53.658
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.634
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.636
Given I shutdown Tails and wait for the computer to power off 14.111
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:48.222
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.347
And the file system changes introduced in version 6.2~testoverlayfs are present 0.579
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.426
# 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.398
When the network is plugged 0.067
And Tor is ready 21.892
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 11.260
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.910
Given I shutdown Tails and wait for the computer to power off 7.038
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:40.991
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.923
And the file system changes introduced in version 6.3~testoverlayfs are present 0.710
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.390
When the network is plugged 0.068
And Tor is ready 26.900
Then the Upgrader considers the system as up-to-date 0.478
# 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 21.642
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.129
After features/support/hooks.rb:330 0.815
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
47.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.593
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.054
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the signing key used by the Upgrader is outdated 0.109
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 22.773
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.978
After features/support/hooks.rb:330 0.979
After features/support/hooks.rb:100 0.000