Project Number Date
test_Tails_ISO_devel 3791 28 Apr 2025, 23:50

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:35.003 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:20.286
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.045
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.739
When I start Tails from USB drive "old" with network unplugged 1:42.158
Then the boot device has safe access rights 3.074
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:330 9.161
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.062
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.284
And I start Tails from USB drive "old" with network unplugged and I login 1:29.617
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 35.874
And I take note of which tps features are available 1.830
Then a Tails persistence partition exists on USB drive "old" 0.767
And I shutdown Tails and wait for the computer to power off 8.323
After features/support/hooks.rb:330 0.198
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.096
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.931
Then Tails is running from USB drive "old" 0.387
And all tps features are active 2.173
When I write some files expected to persist 2.255
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.514
And I take note of which tps features are available 0.387
And I shutdown Tails and wait for the computer to power off 4.247
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.357
After features/support/hooks.rb:330 0.105
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.165
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 11.137
And I log in to a new session 20.511
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.721
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.227
Then the running Tails is installed on USB drive "to_upgrade" 22.677
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:330 1.201
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.343
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.707
Then all tps features from the old Tails version are active 1.646
And Tails is running from USB drive "to_upgrade" 0.459
And the boot device has safe access rights 3.227
And the expected persistent files created with the old Tails version are present in the filesystem 1.489
And all persistent directories from the old Tails version have safe access rights 2.593
After features/support/hooks.rb:330 0.714
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:27.179
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 11.348
And no SquashFS delta is installed 0.197
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.413
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.676
When the network is plugged 0.097
And Tor is ready 21.209
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.893
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.238
Given I shutdown Tails and wait for the computer to power off 9.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.375
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.142
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.384
# 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.281
When the network is plugged 0.071
And Tor is ready 19.083
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.870
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.902
Given I shutdown Tails and wait for the computer to power off 4.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.996
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.058
And the file system changes introduced in version 6.3~testoverlayfs are present 0.594
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.079
And Tor is ready 19.659
Then the Upgrader considers the system as up-to-date 0.307
# 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.308
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.922
After features/support/hooks.rb:330 0.684
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
37.868
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 10.044
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.485
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
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.079
And Tor is ready 20.271
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.842
After features/support/hooks.rb:330 0.858
After features/support/hooks.rb:100 0.000