Project Number Date
test_Tails_ISO_stable 5542 02 Apr 2025, 12: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 22:45.113 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:42.758
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.282
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.077
And I write an old version of the Tails USB image to disk "old" 1:2.266
When I start Tails from USB drive "old" with network unplugged 1:34.654
Then the boot device has safe access rights 3.264
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.361
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:330 7.982
After features/support/hooks.rb:100 0.012
Tags: @product
2:28.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login 1:40.412
Then Tails is running from USB drive "old" 0.596
And I create a persistent partition 34.601
And I take note of which tps features are available 2.331
Then a Tails persistence partition exists on USB drive "old" 0.960
And I shutdown Tails and wait for the computer to power off 9.065
After features/support/hooks.rb:330 0.254
After features/support/hooks.rb:100 0.014
Tags: @product
3:17.369
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.846
Then Tails is running from USB drive "old" 1.080
And all tps features are active 2.974
When I write some files expected to persist 2.025
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.292
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.730
And I take note of which tps features are available 0.640
And I shutdown Tails and wait for the computer to power off 6.928
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.118
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.012
Tags: @product
3:5.167
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 without a persistent partition and stopped at Tails Greeter's login screen 23.846
And I log in to a new session 20.389
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.822
And I plug USB drive "to_upgrade" 2.503
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.933
Then the running Tails is installed on USB drive "to_upgrade" 33.117
And I unplug USB drive "to_upgrade" 0.301
And I unplug USB drive "__internal" 0.252
After features/support/hooks.rb:330 7.371
After features/support/hooks.rb:100 0.000
Tags: @product
2:48.297
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Given a computer 0.809
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:36.381
Then all tps features from the old Tails version are active 1.879
And Tails is running from USB drive "to_upgrade" 0.367
And the boot device has safe access rights 4.336
And the expected persistent files created with the old Tails version are present in the filesystem 1.559
And all persistent directories from the old Tails version have safe access rights 2.962
After features/support/hooks.rb:330 1.665
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:23.587
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 20.439
And no SquashFS delta is installed 0.366
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.405
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.346
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.498
When the network is plugged 0.081
And Tor is ready 24.361
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.373
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.188
Given I shutdown Tails and wait for the computer to power off 13.861
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.190
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.648
And the file system changes introduced in version 6.2~testoverlayfs are present 0.414
And only the 6.2~testoverlayfs SquashFS delta is installed 0.122
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.366
When the network is plugged 0.102
And Tor is ready 18.441
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.481
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.682
Given I shutdown Tails and wait for the computer to power off 4.696
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.611
Then Tails is running version 6.3~testoverlayfs 0.033
And all tps features are active 4.619
And the file system changes introduced in version 6.3~testoverlayfs are present 0.722
And only the 6.3~testoverlayfs SquashFS delta is installed 0.109
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.392
When the network is plugged 0.115
And Tor is ready 22.367
Then the Upgrader considers the system as up-to-date 0.431
# 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.170
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.207
After features/support/hooks.rb:330 0.748
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
59.707
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 28.034
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.373
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.113
But a current signing key is available on our website 0.000
When the network is plugged 0.947
And Tor is ready 21.472
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.673
After features/support/hooks.rb:330 0.809
After features/support/hooks.rb:100 0.000