Project Number Date
test_Tails_ISO_stable 4968 24 Jul 2024, 08:35

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:10.535 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:5.032
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.656
When I start Tails from USB drive "old" with network unplugged 1:28.657
Then the boot device has safe access rights 3.338
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 8.804
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.784
Before features/support/hooks.rb:269 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:24.310
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 32.501
And I take note of which tps features are available 2.017
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 8.578
After features/support/hooks.rb:326 0.226
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.793
Before features/support/hooks.rb:269 0.007
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.243
Then Tails is running from USB drive "old" 0.395
And all tps features are active 2.066
When I write some files expected to persist 1.825
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.278
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.715
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.218
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.941
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.011
Tags: @product
2:28.289
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.144
And I log in to a new session 21.448
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.513
And I plug USB drive "to_upgrade" 2.374
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.608
Then the running Tails is installed on USB drive "to_upgrade" 16.793
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 4.527
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.473
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.127
Then all tps features from the old Tails version are active 1.567
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.121
And the expected persistent files created with the old Tails version are present in the filesystem 1.453
And all persistent directories from the old Tails version have safe access rights 2.690
After features/support/hooks.rb:326 0.708
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:39.940
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.149
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.435
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.054
And Tor is ready 19.828
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.197
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.023
Given I shutdown Tails and wait for the computer to power off 10.992
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.680
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.047
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.302
When the network is plugged 0.043
And Tor is ready 17.428
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.863
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.093
Given I shutdown Tails and wait for the computer to power off 4.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.594
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.143
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.039
And Tor is ready 18.171
Then the Upgrader considers the system as up-to-date 0.360
# 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 14.876
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.178
After features/support/hooks.rb:326 0.724
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.221
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.961
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.375
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.810
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 19.332
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.617
After features/support/hooks.rb:326 0.867
After features/support/hooks.rb:100 0.000