Project Number Date
test_Tails_ISO_stable 5607 29 Apr 2025, 12:48

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:53.677 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:31.996
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 1.594
And I create a 7200 MiB disk named "old" 0.623
And I plug USB drive "old" 1.304
And I write an old version of the Tails USB image to disk "old" 37.398
When I start Tails from USB drive "old" with network unplugged 1:46.454
Then the boot device has safe access rights 3.545
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.106
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 7.288
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.986
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 1.589
And I start Tails from USB drive "old" with network unplugged and I login 1:37.528
Then Tails is running from USB drive "old" 0.409
And I create a persistent partition 38.687
And I take note of which tps features are available 5.780
Then a Tails persistence partition exists on USB drive "old" 1.443
And I shutdown Tails and wait for the computer to power off 7.547
After features/support/hooks.rb:330 0.211
After features/support/hooks.rb:100 0.011
Tags: @product
3:31.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.981
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:46.313
Then Tails is running from USB drive "old" 0.378
And all tps features are active 3.995
When I write some files expected to persist 2.299
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.290
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 3.097
And I take note of which tps features are available 0.693
And I shutdown Tails and wait for the computer to power off 6.428
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.650
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.470
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 20.220
And I log in to a new session 22.257
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.095
And I plug USB drive "to_upgrade" 2.485
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.860
Then the running Tails is installed on USB drive "to_upgrade" 28.918
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.413
After features/support/hooks.rb:330 1.257
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.714
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.251
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.594
Then all tps features from the old Tails version are active 2.412
And Tails is running from USB drive "to_upgrade" 0.639
And the boot device has safe access rights 3.905
And the expected persistent files created with the old Tails version are present in the filesystem 1.947
And all persistent directories from the old Tails version have safe access rights 2.962
After features/support/hooks.rb:330 1.460
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:59.187
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 21.398
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.877
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.336
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.149
And Tor is ready 54.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.584
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.334
Given I shutdown Tails and wait for the computer to power off 11.503
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.084
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 3.094
And the file system changes introduced in version 6.2~testoverlayfs are present 0.354
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.499
# 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.420
When the network is plugged 0.106
And Tor is ready 22.205
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.311
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.318
Given I shutdown Tails and wait for the computer to power off 7.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.682
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.961
And the file system changes introduced in version 6.3~testoverlayfs are present 0.742
And only the 6.3~testoverlayfs SquashFS delta is installed 0.112
# 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.352
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.455
When the network is plugged 0.114
And Tor is ready 19.825
Then the Upgrader considers the system as up-to-date 0.329
# 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 17.060
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.119
After features/support/hooks.rb:330 1.164
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
41.729
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 10.703
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 20.988
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.370
After features/support/hooks.rb:330 1.679
After features/support/hooks.rb:100 0.000