Project Number Date
test_Tails_ISO_stable 5584 19 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 20:9.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:13.881
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.505
When I start Tails from USB drive "old" with network unplugged 1:38.141
Then the boot device has safe access rights 2.943
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 7.225
After features/support/hooks.rb:100 0.025
Tags: @product
2:14.133
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.838
And I start Tails from USB drive "old" with network unplugged and I login 1:29.520
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 31.934
And I take note of which tps features are available 2.272
Then a Tails persistence partition exists on USB drive "old" 0.795
And I shutdown Tails and wait for the computer to power off 8.399
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.729
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.017
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.951
When I write some files expected to persist 1.787
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.478
And all persistent directories from the old Tails version have safe access rights 2.469
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 4.285
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.498
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.822
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.327
And I log in to a new session 18.984
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.642
And I plug USB drive "to_upgrade" 2.378
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.288
Then the running Tails is installed on USB drive "to_upgrade" 24.783
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 1.005
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.602
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.808
Then all tps features from the old Tails version are active 1.755
And Tails is running from USB drive "to_upgrade" 0.452
And the boot device has safe access rights 3.517
And the expected persistent files created with the old Tails version are present in the filesystem 1.375
And all persistent directories from the old Tails version have safe access rights 2.493
After features/support/hooks.rb:330 1.398
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:24.838
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.834
And no SquashFS delta is installed 0.196
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.444
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.108
And Tor is ready 21.676
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.919
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.388
Given I shutdown Tails and wait for the computer to power off 12.846
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.154
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.435
And the file system changes introduced in version 6.2~testoverlayfs are present 0.352
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.330
When the network is plugged 0.064
And Tor is ready 17.665
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.662
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.276
Given I shutdown Tails and wait for the computer to power off 4.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.207
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.962
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.478
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.360
When the network is plugged 0.106
And Tor is ready 48.984
Then the Upgrader considers the system as up-to-date 0.328
# 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.575
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.480
After features/support/hooks.rb:330 0.707
After features/support/hooks.rb:100 0.040
Tags: @product @automatic_upgrade
37.098
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 10.216
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.613
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 18.075
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.981
After features/support/hooks.rb:330 0.720
After features/support/hooks.rb:100 0.000