Project Number Date
test_Tails_ISO_stable 4792 17 Apr 2024, 15:41

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 16:55.546 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:47.435
Before features/support/hooks.rb:259 0.006
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.140
And I write an old version of the Tails USB image to disk "old" 22.282
When I start Tails from USB drive "old" with network unplugged 1:20.005
Then the boot device has safe access rights 2.859
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:305 3.488
After features/support/hooks.rb:89 0.035
Tags: @product
2:8.858
Before features/support/hooks.rb:259 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:23.624
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 34.295
And I take note of which tps features are available 1.278
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 8.387
After features/support/hooks.rb:305 0.223
After features/support/hooks.rb:89 0.008
Tags: @product
2:25.922
Before features/support/hooks.rb:259 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.392
Then Tails is running from USB drive "old" 0.315
And all tps features are active 1.873
When I write some files expected to persist 1.541
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 2.793
And I take note of which tps features are available 0.371
And I shutdown Tails and wait for the computer to power off 4.248
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.566
After features/support/hooks.rb:305 0.138
After features/support/hooks.rb:89 0.010
Tags: @product
2:19.402
Before features/support/hooks.rb:259 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 9.941
And I log in to a new session 16.289
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.463
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.516
Then the running Tails is installed on USB drive "to_upgrade" 15.415
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:305 2.552
After features/support/hooks.rb:89 0.000
Tags: @product
1:56.862
Before features/support/hooks.rb:259 0.007
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.366
Then all tps features from the old Tails version are active 1.462
And Tails is running from USB drive "to_upgrade" 0.287
And the boot device has safe access rights 2.780
And the expected persistent files created with the old Tails version are present in the filesystem 1.287
And all persistent directories from the old Tails version have safe access rights 2.486
After features/support/hooks.rb:305 0.723
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
5:46.284
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.220
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.233
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.042
And Tor is ready 19.428
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.092
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.350
Given I shutdown Tails and wait for the computer to power off 6.410
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.704
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.940
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.264
When the network is plugged 0.042
And Tor is ready 15.619
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.017
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.384
Given I shutdown Tails and wait for the computer to power off 4.218
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.746
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.873
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.036
And Tor is ready 17.833
Then the Upgrader considers the system as up-to-date 0.243
# 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.126
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.871
After features/support/hooks.rb:305 0.724
After features/support/hooks.rb:89 0.020
Tags: @product @automatic_upgrade
30.779
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.446
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 16.109
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.777
After features/support/hooks.rb:305 0.663
After features/support/hooks.rb:89 0.000