Project Number Date
test_Tails_ISO_stable 5601 27 Apr 2025, 12:55

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:45.035 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:15.608
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 34.269
When I start Tails from USB drive "old" with network unplugged 1:35.751
Then the boot device has safe access rights 3.103
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.134
And udev-watchdog is monitoring the correct device 0.369
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:330 3.738
After features/support/hooks.rb:100 0.022
Tags: @product
2:12.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:27.727
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 33.096
And I take note of which tps features are available 1.840
Then a Tails persistence partition exists on USB drive "old" 0.782
And I shutdown Tails and wait for the computer to power off 8.716
After features/support/hooks.rb:330 0.198
After features/support/hooks.rb:100 0.016
Tags: @product
2:54.373
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.144
Then Tails is running from USB drive "old" 0.382
And all tps features are active 2.160
When I write some files expected to persist 1.849
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.596
And all persistent directories from the old Tails version have safe access rights 2.589
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 4.432
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.312
After features/support/hooks.rb:330 0.235
After features/support/hooks.rb:100 0.014
Tags: @product
2:36.243
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 without a persistent partition and stopped at Tails Greeter's login screen 10.814
And I log in to a new session 20.671
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.854
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.524
Then the running Tails is installed on USB drive "to_upgrade" 26.513
And I unplug USB drive "to_upgrade" 0.253
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 2.220
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.127
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.240
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.850
Then all tps features from the old Tails version are active 1.750
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.647
And the expected persistent files created with the old Tails version are present in the filesystem 1.562
And all persistent directories from the old Tails version have safe access rights 2.664
After features/support/hooks.rb:330 1.048
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:43.491
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.673
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.651
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.585
When the network is plugged 0.067
And Tor is ready 24.462
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.989
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.101
Given I shutdown Tails and wait for the computer to power off 9.042
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.391
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.763
And the file system changes introduced in version 6.2~testoverlayfs are present 0.432
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.437
When the network is plugged 0.103
And Tor is ready 18.974
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.896
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.943
Given I shutdown Tails and wait for the computer to power off 4.949
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.189
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.215
And the file system changes introduced in version 6.3~testoverlayfs are present 0.639
And only the 6.3~testoverlayfs SquashFS delta is installed 0.106
# 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.361
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.420
When the network is plugged 0.381
And Tor is ready 19.710
Then the Upgrader considers the system as up-to-date 0.357
# 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 16.154
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.494
After features/support/hooks.rb:330 0.802
After features/support/hooks.rb:100 0.049
Tags: @product @automatic_upgrade
38.464
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 11.351
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.600
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.154
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 18.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.538
After features/support/hooks.rb:330 1.134
After features/support/hooks.rb:100 0.000