Project Number Date
test_Tails_ISO_devel 3815 16 May 2025, 13:13

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 20:29.652 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:23.280
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 33.300
When I start Tails from USB drive "old" with network unplugged 1:44.378
Then the boot device has safe access rights 3.211
And Tails is running from USB drive "old" 0.397
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 3.760
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:31.112
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 32.425
And I take note of which tps features are available 1.687
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 8.502
After features/support/hooks.rb:330 0.200
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.694
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.126
Then Tails is running from USB drive "old" 0.423
And all tps features are active 2.209
When I write some files expected to persist 1.883
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.454
And all persistent directories from the old Tails version have safe access rights 3.026
And I take note of which tps features are available 0.544
And I shutdown Tails and wait for the computer to power off 6.542
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.019
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.010
Tags: @product
2:42.440
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.591
And I log in to a new session 21.371
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.742
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.997
Then the running Tails is installed on USB drive "to_upgrade" 26.934
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 7.055
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.707
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.001
Then all tps features from the old Tails version are active 1.843
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 4.050
And the expected persistent files created with the old Tails version are present in the filesystem 1.693
And all persistent directories from the old Tails version have safe access rights 2.600
After features/support/hooks.rb:330 1.165
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:1.266
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 14.896
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.386
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.662
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.497
When the network is plugged 0.125
And Tor is ready 24.067
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.670
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.036
Given I shutdown Tails and wait for the computer to power off 11.051
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.370
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.665
And the file system changes introduced in version 6.2~testoverlayfs are present 0.386
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.450
# 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.331
When the network is plugged 0.076
And Tor is ready 16.399
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.519
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.572
Given I shutdown Tails and wait for the computer to power off 6.625
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.502
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 3.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.569
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.385
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.086
And Tor is ready 20.044
Then the Upgrader considers the system as up-to-date 0.314
# 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.843
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.882
After features/support/hooks.rb:330 0.737
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
39.118
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 11.464
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.370
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 20.180
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.897
After features/support/hooks.rb:330 1.246
After features/support/hooks.rb:100 0.000