Project Number Date
test_Tails_ISO_stable 4880 10 Jun 2024, 12:18

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:9.243 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:54.772
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.496
When I start Tails from USB drive "old" with network unplugged 1:20.214
Then the boot device has safe access rights 2.837
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:315 3.584
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.306
Before features/support/hooks.rb:269 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:29.940
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 33.996
And I take note of which tps features are available 1.395
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.656
After features/support/hooks.rb:315 0.132
After features/support/hooks.rb:100 0.015
Tags: @product
2:36.201
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.069
Then Tails is running from USB drive "old" 0.345
And all tps features are active 1.807
When I write some files expected to persist 1.646
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 2.269
And I take note of which tps features are available 0.359
And I shutdown Tails and wait for the computer to power off 4.668
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.164
After features/support/hooks.rb:315 0.121
After features/support/hooks.rb:100 0.017
Tags: @product
2:28.434
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 10.075
And I log in to a new session 17.863
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.602
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.721
Then the running Tails is installed on USB drive "to_upgrade" 16.338
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:315 6.694
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.661
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.030
Then all tps features from the old Tails version are active 1.539
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 2.952
And the expected persistent files created with the old Tails version are present in the filesystem 1.429
And all persistent directories from the old Tails version have safe access rights 2.235
After features/support/hooks.rb:315 0.782
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:12.203
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 10.314
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.380
When the network is plugged 0.103
And Tor is ready 21.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.562
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.586
Given I shutdown Tails and wait for the computer to power off 8.550
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.722
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.497
And the file system changes introduced in version 6.2~testoverlayfs are present 0.267
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.256
When the network is plugged 0.074
And Tor is ready 16.476
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.406
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.450
Given I shutdown Tails and wait for the computer to power off 4.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.975
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.926
And the file system changes introduced in version 6.3~testoverlayfs are present 0.438
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.027
And Tor is ready 17.016
Then the Upgrader considers the system as up-to-date 10.720
# 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.087
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.885
After features/support/hooks.rb:315 0.768
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
32.663
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 9.748
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 1.010
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 14.883
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.597
After features/support/hooks.rb:315 1.840
After features/support/hooks.rb:100 0.000