Project Number Date
test_Tails_ISO_devel 3744 18 Mar 2025, 19:51

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 21:42.286 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:24.902
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Given a computer 1.374
And I create a 7200 MiB disk named "old" 0.088
And I plug USB drive "old" 1.136
And I write an old version of the Tails USB image to disk "old" 35.755
When I start Tails from USB drive "old" with network unplugged 1:41.851
Then the boot device has safe access rights 3.518
And Tails is running from USB drive "old" 0.438
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.371
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 7.691
After features/support/hooks.rb:100 0.013
Tags: @product
2:23.424
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:34.400
Then Tails is running from USB drive "old" 0.417
And I create a persistent partition 34.383
And I take note of which tps features are available 2.526
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 10.656
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.007
Tags: @product
3:18.268
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:40.314
Then Tails is running from USB drive "old" 0.402
And all tps features are active 2.338
When I write some files expected to persist 1.979
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.471
And all persistent directories from the old Tails version have safe access rights 2.637
And I take note of which tps features are available 0.515
And I shutdown Tails and wait for the computer to power off 4.358
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.829
After features/support/hooks.rb:330 0.134
After features/support/hooks.rb:100 0.011
Tags: @product
2:40.841
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.049
And I log in to a new session 26.371
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.497
And I plug USB drive "to_upgrade" 2.541
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.552
Then the running Tails is installed on USB drive "to_upgrade" 21.366
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.247
After features/support/hooks.rb:330 1.636
After features/support/hooks.rb:100 0.000
Tags: @product
2:42.995
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:32.167
Then all tps features from the old Tails version are active 1.890
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.685
And the expected persistent files created with the old Tails version are present in the filesystem 2.099
And all persistent directories from the old Tails version have safe access rights 2.568
After features/support/hooks.rb:330 1.642
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:10.379
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 13.548
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.449
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.677
When the network is plugged 0.070
And Tor is ready 49.200
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.632
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.854
Given I shutdown Tails and wait for the computer to power off 12.059
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.900
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.448
And the file system changes introduced in version 6.2~testoverlayfs are present 0.361
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.357
# 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.337
When the network is plugged 0.089
And Tor is ready 18.214
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.674
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.369
Given I shutdown Tails and wait for the computer to power off 4.595
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.670
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.938
And the file system changes introduced in version 6.3~testoverlayfs are present 0.575
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.083
And Tor is ready 20.924
Then the Upgrader considers the system as up-to-date 0.372
# 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.570
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.128
After features/support/hooks.rb:330 0.726
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
1:1.474
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 11.041
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 49.204
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.611
After features/support/hooks.rb:330 2.243
After features/support/hooks.rb:100 0.000