Project Number Date
test_Tails_ISO_devel 3756 26 Mar 2025, 19:30

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 23:11.102 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:43.628
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.389
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 35.099
When I start Tails from USB drive "old" with network unplugged 2:2.529
Then the boot device has safe access rights 3.302
And Tails is running from USB drive "old" 0.424
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:330 8.186
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.360
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login 1:32.693
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 32.182
And I take note of which tps features are available 1.988
Then a Tails persistence partition exists on USB drive "old" 0.866
And I shutdown Tails and wait for the computer to power off 8.997
After features/support/hooks.rb:330 0.239
After features/support/hooks.rb:100 0.013
Tags: @product
3:21.245
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.648
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:39.380
Then Tails is running from USB drive "old" 0.388
And all tps features are active 2.318
When I write some files expected to persist 2.039
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.645
And I take note of which tps features are available 0.643
And I shutdown Tails and wait for the computer to power off 6.729
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.776
After features/support/hooks.rb:330 0.108
After features/support/hooks.rb:100 0.044
Tags: @product
3:6.505
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 23.962
And I log in to a new session 21.483
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.091
And I plug USB drive "to_upgrade" 2.554
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.706
Then the running Tails is installed on USB drive "to_upgrade" 30.754
And I unplug USB drive "to_upgrade" 0.476
And I unplug USB drive "__internal" 0.476
After features/support/hooks.rb:330 2.839
After features/support/hooks.rb:100 0.000
Tags: @product
2:41.501
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 1.769
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:27.966
Then all tps features from the old Tails version are active 2.283
And Tails is running from USB drive "to_upgrade" 0.367
And the boot device has safe access rights 4.284
And the expected persistent files created with the old Tails version are present in the filesystem 1.826
And all persistent directories from the old Tails version have safe access rights 3.001
After features/support/hooks.rb:330 1.576
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
7:56.243
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 with a persistent partition enabled and logged in 29.486
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.461
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.501
When the network is plugged 0.083
And Tor is ready 24.018
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.185
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.558
Given I shutdown Tails and wait for the computer to power off 9.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.436
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.928
And the file system changes introduced in version 6.2~testoverlayfs are present 0.560
And only the 6.2~testoverlayfs SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.375
# 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.334
When the network is plugged 0.094
And Tor is ready 19.961
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.072
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.122
Given I shutdown Tails and wait for the computer to power off 7.465
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:34.484
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.718
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.079
And Tor is ready 19.641
Then the Upgrader considers the system as up-to-date 0.336
# 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 16.534
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.998
After features/support/hooks.rb:330 0.855
After features/support/hooks.rb:100 0.091
Tags: @product @automatic_upgrade
1:4.617
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.528
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.098
And Tor is ready 48.810
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.675
After features/support/hooks.rb:330 1.129
After features/support/hooks.rb:100 0.000