Project Number Date
test_Tails_ISO_devel 3275 11 Feb 2024, 18:24

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 88 0 0 0 0 88 7 0 7 18:54.987 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
1:38.447
Before features/support/hooks.rb:245 0.003
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 20.601
When I start Tails from USB drive "old" with network unplugged 1:12.140
Then the boot device has safe access rights 3.310
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.099
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.415
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:291 7.137
After features/support/hooks.rb:75 0.006
Tags: @product
2:7.649
Before features/support/hooks.rb:245 0.002
Given a computer 0.129
And I start Tails from USB drive "old" with network unplugged and I login 1:16.090
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 40.651
And I take note of which tps features are available 1.650
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 8.066
After features/support/hooks.rb:291 0.200
After features/support/hooks.rb:75 0.006
Tags: @product
2:52.649
Before features/support/hooks.rb:245 0.002
Given a computer 0.152
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.084
Then Tails is running from USB drive "old" 0.431
And all tps features are active 2.085
When I write some files expected to persist 1.890
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.479
And all persistent directories from the old Tails version have safe access rights 2.606
And I take note of which tps features are available 0.500
And I shutdown Tails and wait for the computer to power off 5.110
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.030
After features/support/hooks.rb:291 0.175
After features/support/hooks.rb:75 0.006
Tags: @product
2:36.422
Before features/support/hooks.rb:245 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.511
And I log in to a new session 19.998
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.455
And I plug USB drive "to_upgrade" 2.466
And I cancel the GNOME authentication prompt 1.887
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.380
Then the running Tails is installed on USB drive "to_upgrade" 14.307
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:291 1.902
After features/support/hooks.rb:75 0.000
Tags: @product
2:24.043
Before features/support/hooks.rb:245 0.004
Given a computer 0.160
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.013
Then all tps features from the old Tails version are active 1.723
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.422
And the expected persistent files created with the old Tails version are present in the filesystem 1.594
And all persistent directories from the old Tails version have safe access rights 2.774
After features/support/hooks.rb:291 1.117
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
6:42.081
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.902
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.368
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.463
When the network is plugged 0.032
And Tor is ready 17.836
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.125
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.049
Given I shutdown Tails and wait for the computer to power off 7.332
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.352
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.012
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
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.302
# 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.272
When the network is plugged 0.048
And Tor is ready 18.641
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.132
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.661
Given I shutdown Tails and wait for the computer to power off 4.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.234
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.047
And Tor is ready 15.051
Then the Upgrader considers the system as up-to-date 0.286
# 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.302
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.122
After features/support/hooks.rb:291 0.743
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
33.694
Before features/support/hooks.rb:245 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.767
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.474
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.474
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 16.848
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.012
After features/support/hooks.rb:291 0.662
After features/support/hooks.rb:75 0.000