Project Number Date
test_Tails_ISO_stable 5586 21 Apr 2025, 13:31

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:40.107 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:8.982
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 32.108
When I start Tails from USB drive "old" with network unplugged 1:31.602
Then the boot device has safe access rights 3.039
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 3.526
After features/support/hooks.rb:100 0.038
Tags: @product
2:10.036
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:27.037
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 31.780
And I take note of which tps features are available 1.640
Then a Tails persistence partition exists on USB drive "old" 0.790
And I shutdown Tails and wait for the computer to power off 8.276
After features/support/hooks.rb:330 0.136
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.048
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.797
Then Tails is running from USB drive "old" 0.292
And all tps features are active 2.283
When I write some files expected to persist 1.978
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 2.498
And I take note of which tps features are available 0.501
And I shutdown Tails and wait for the computer to power off 4.654
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.241
After features/support/hooks.rb:330 0.140
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.236
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 10.549
And I log in to a new session 18.394
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.709
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.133
Then the running Tails is installed on USB drive "to_upgrade" 24.611
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 1.010
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.609
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.850
Then all tps features from the old Tails version are active 1.634
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.619
And the expected persistent files created with the old Tails version are present in the filesystem 1.423
And all persistent directories from the old Tails version have safe access rights 2.584
After features/support/hooks.rb:330 1.509
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:52.079
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 24.723
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.604
When the network is plugged 0.074
And Tor is ready 20.580
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.738
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.406
Given I shutdown Tails and wait for the computer to power off 8.831
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.931
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.059
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.249
When the network is plugged 0.074
And Tor is ready 17.620
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.517
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.120
Given I shutdown Tails and wait for the computer to power off 4.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.945
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.341
And the file system changes introduced in version 6.3~testoverlayfs are present 0.559
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.082
And Tor is ready 19.793
Then the Upgrader considers the system as up-to-date 0.330
# 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 15.552
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.427
After features/support/hooks.rb:330 0.781
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
36.113
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.301
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 19.649
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.665
After features/support/hooks.rb:330 0.811
After features/support/hooks.rb:100 0.000