Project Number Date
test_Tails_ISO_stable 5394 15 Jan 2025, 17:07

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 22:11.473 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
3:17.592
Before features/support/hooks.rb:269 0.006
Given a computer 0.388
And I create a 7200 MiB disk named "old" 0.079
And I plug USB drive "old" 1.084
And I write an old version of the Tails USB image to disk "old" 1:24.070
When I start Tails from USB drive "old" with network unplugged 1:47.600
Then the boot device has safe access rights 3.328
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 3.693
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.299
Before features/support/hooks.rb:269 0.006
Given a computer 0.276
And I start Tails from USB drive "old" with network unplugged and I login 1:31.810
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 41.018
And I take note of which tps features are available 2.098
Then a Tails persistence partition exists on USB drive "old" 1.019
And I shutdown Tails and wait for the computer to power off 8.719
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.008
Tags: @product
3:17.327
Before features/support/hooks.rb:269 0.004
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.803
Then Tails is running from USB drive "old" 0.358
And all tps features are active 2.535
When I write some files expected to persist 1.946
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.667
And I take note of which tps features are available 0.633
And I shutdown Tails and wait for the computer to power off 4.560
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.841
After features/support/hooks.rb:326 0.270
After features/support/hooks.rb:100 0.012
Tags: @product
2:48.975
Before features/support/hooks.rb:269 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 15.871
And I log in to a new session 21.050
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.277
And I plug USB drive "to_upgrade" 2.496
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.017
Then the running Tails is installed on USB drive "to_upgrade" 23.792
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:326 2.511
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.368
Before features/support/hooks.rb:269 0.005
Given a computer 0.264
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.472
Then all tps features from the old Tails version are active 2.040
And Tails is running from USB drive "to_upgrade" 0.482
And the boot device has safe access rights 3.584
And the expected persistent files created with the old Tails version are present in the filesystem 1.674
And all persistent directories from the old Tails version have safe access rights 2.850
After features/support/hooks.rb:326 0.676
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:14.158
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.426
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.092
And Tor is ready 23.404
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.031
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.105
Given I shutdown Tails and wait for the computer to power off 11.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.462
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.821
And the file system changes introduced in version 6.2~testoverlayfs are present 0.414
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.362
# 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.357
When the network is plugged 0.106
And Tor is ready 18.221
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.314
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.223
Given I shutdown Tails and wait for the computer to power off 6.643
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.179
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 3.892
And the file system changes introduced in version 6.3~testoverlayfs are present 0.758
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.505
When the network is plugged 0.093
And Tor is ready 19.837
Then the Upgrader considers the system as up-to-date 0.345
# 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.151
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.297
After features/support/hooks.rb:326 1.099
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
40.752
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.561
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 21.671
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.139
After features/support/hooks.rb:326 0.712
After features/support/hooks.rb:100 0.000