Project Number Date
test_Tails_ISO_stable 4951 17 Jul 2024, 08:44

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 20:0.091 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:26.615
Before features/support/hooks.rb:269 0.007
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 33.317
When I start Tails from USB drive "old" with network unplugged 1:47.765
Then the boot device has safe access rights 3.108
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 3.533
After features/support/hooks.rb:100 0.011
Tags: @product
2:8.870
Before features/support/hooks.rb:269 0.005
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login 1:24.117
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 32.039
And I take note of which tps features are available 2.186
Then a Tails persistence partition exists on USB drive "old" 1.043
And I shutdown Tails and wait for the computer to power off 8.878
After features/support/hooks.rb:326 0.203
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.224
Before features/support/hooks.rb:269 0.006
Given a computer 0.525
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.513
Then Tails is running from USB drive "old" 0.400
And all tps features are active 2.490
When I write some files expected to persist 2.249
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.298
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 2.812
And I take note of which tps features are available 0.648
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.573
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.298
Before features/support/hooks.rb:269 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 24.876
And I log in to a new session 19.801
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.452
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.267
Then the running Tails is installed on USB drive "to_upgrade" 25.012
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 2.783
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.143
Before features/support/hooks.rb:269 0.006
Given a computer 0.274
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.895
Then all tps features from the old Tails version are active 1.782
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 3.631
And the expected persistent files created with the old Tails version are present in the filesystem 1.476
And all persistent directories from the old Tails version have safe access rights 2.702
After features/support/hooks.rb:326 0.987
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:28.846
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.466
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.336
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.500
When the network is plugged 0.037
And Tor is ready 21.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.930
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.723
Given I shutdown Tails and wait for the computer to power off 11.370
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.984
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.376
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.280
When the network is plugged 0.047
And Tor is ready 22.877
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.997
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.584
Given I shutdown Tails and wait for the computer to power off 4.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.424
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.387
And the file system changes introduced in version 6.3~testoverlayfs are present 0.650
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.455
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.393
When the network is plugged 0.044
And Tor is ready 18.954
Then the Upgrader considers the system as up-to-date 0.413
# 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.966
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.235
After features/support/hooks.rb:326 0.747
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
37.092
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 11.344
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.067
And the signing key used by the Upgrader is outdated 0.971
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 17.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.660
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.000