Project Number Date
test_Tails_ISO_stable 4699 05 Mar 2024, 12:20

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 18:41.871 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:39.564
Before features/support/hooks.rb:245 0.005
Given a computer 0.155
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 20.001
When I start Tails from USB drive "old" with network unplugged 1:14.047
Then the boot device has safe access rights 3.220
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:291 6.651
After features/support/hooks.rb:75 0.009
Tags: @product
2:8.501
Before features/support/hooks.rb:245 0.006
Given a computer 0.154
And I start Tails from USB drive "old" with network unplugged and I login 1:16.595
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 40.682
And I take note of which tps features are available 1.929
Then a Tails persistence partition exists on USB drive "old" 0.758
And I shutdown Tails and wait for the computer to power off 8.070
After features/support/hooks.rb:291 0.154
After features/support/hooks.rb:75 0.011
Tags: @product
2:36.150
Before features/support/hooks.rb:245 0.006
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.275
Then Tails is running from USB drive "old" 0.334
And all tps features are active 1.717
When I write some files expected to persist 1.706
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.536
And I take note of which tps features are available 0.329
And I shutdown Tails and wait for the computer to power off 4.024
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.433
After features/support/hooks.rb:291 0.217
After features/support/hooks.rb:75 0.011
Tags: @product
2:31.465
Before features/support/hooks.rb:245 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 10.855
And I log in to a new session 17.396
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.450
And I plug USB drive "to_upgrade" 2.509
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.727
Then the running Tails is installed on USB drive "to_upgrade" 13.121
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:291 3.618
After features/support/hooks.rb:75 0.000
Tags: @product
2:22.006
Before features/support/hooks.rb:245 0.007
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.181
Then all tps features from the old Tails version are active 1.480
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.206
And the expected persistent files created with the old Tails version are present in the filesystem 1.387
And all persistent directories from the old Tails version have safe access rights 2.221
After features/support/hooks.rb:291 0.644
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
6:37.709
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.070
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
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.442
When the network is plugged 0.035
And Tor is ready 16.834
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.095
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.223
Given I shutdown Tails and wait for the computer to power off 6.030
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.599
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.920
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.285
When the network is plugged 0.031
And Tor is ready 17.210
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.441
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.585
Given I shutdown Tails and wait for the computer to power off 4.022
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.235
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.873
And the file system changes introduced in version 6.3~testoverlayfs are present 0.539
And only the 6.3~testoverlayfs SquashFS delta is installed 0.105
# 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.389
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.047
And Tor is ready 16.036
Then the Upgrader considers the system as up-to-date 0.294
# 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 13.643
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.879
After features/support/hooks.rb:291 0.764
After features/support/hooks.rb:75 0.088
Tags: @product @automatic_upgrade
46.473
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 22.284
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
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.462
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 17.511
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.664
After features/support/hooks.rb:291 0.894
After features/support/hooks.rb:75 0.000