Project Number Date
test_Tails_ISO_devel 3738 14 Mar 2025, 11:14

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:21.113 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:16.148
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.826
When I start Tails from USB drive "old" with network unplugged 1:39.962
Then the boot device has safe access rights 3.026
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.371
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 0.942
After features/support/hooks.rb:100 0.038
Tags: @product
2:4.432
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login 1:20.792
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 32.511
And I take note of which tps features are available 1.387
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 8.354
After features/support/hooks.rb:330 0.177
After features/support/hooks.rb:100 0.008
Tags: @product
2:49.504
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.802
Then Tails is running from USB drive "old" 0.388
And all tps features are active 2.114
When I write some files expected to persist 1.772
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.541
And I take note of which tps features are available 0.555
And I shutdown Tails and wait for the computer to power off 4.325
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.201
After features/support/hooks.rb:330 0.102
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.448
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 without a persistent partition and stopped at Tails Greeter's login screen 13.371
And I log in to a new session 19.374
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.114
And I plug USB drive "to_upgrade" 2.503
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.566
Then the running Tails is installed on USB drive "to_upgrade" 25.128
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:330 2.816
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.792
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.505
Then all tps features from the old Tails version are active 1.621
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.351
And the expected persistent files created with the old Tails version are present in the filesystem 1.406
And all persistent directories from the old Tails version have safe access rights 2.378
After features/support/hooks.rb:330 0.776
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:33.695
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 12.167
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.609
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.364
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.518
When the network is plugged 0.144
And Tor is ready 22.893
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.750
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.788
Given I shutdown Tails and wait for the computer to power off 10.812
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.258
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.973
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.358
When the network is plugged 0.065
And Tor is ready 16.499
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.925
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.707
Given I shutdown Tails and wait for the computer to power off 4.458
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.220
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.017
And the file system changes introduced in version 6.3~testoverlayfs are present 0.618
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.072
And Tor is ready 20.329
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.230
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.932
After features/support/hooks.rb:330 0.789
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.090
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 9.974
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.129
But a current signing key is available on our website 0.000
When the network is plugged 0.098
And Tor is ready 21.132
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.270
After features/support/hooks.rb:330 0.642
After features/support/hooks.rb:100 0.000