Project Number Date
test_Tails_ISO_stable 4939 14 Jul 2024, 12:10

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:59.346 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:19.245
Before features/support/hooks.rb:269 0.006
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.766
When I start Tails from USB drive "old" with network unplugged 1:45.284
Then the boot device has safe access rights 2.977
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.527
After features/support/hooks.rb:100 0.011
Tags: @product
1:59.383
Before features/support/hooks.rb:269 0.007
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:17.479
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 31.119
And I take note of which tps features are available 1.311
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 8.165
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.589
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.490
Then Tails is running from USB drive "old" 0.298
And all tps features are active 1.939
When I write some files expected to persist 1.611
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.324
And all persistent directories from the old Tails version have safe access rights 2.308
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 4.366
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.347
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.605
Before features/support/hooks.rb:269 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 10.071
And I log in to a new session 16.961
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.468
And I plug USB drive "to_upgrade" 2.382
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.865
Then the running Tails is installed on USB drive "to_upgrade" 15.469
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:326 2.016
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.166
Before features/support/hooks.rb:269 0.007
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.386
Then all tps features from the old Tails version are active 1.484
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 3.217
And the expected persistent files created with the old Tails version are present in the filesystem 1.389
And all persistent directories from the old Tails version have safe access rights 2.199
After features/support/hooks.rb:326 0.861
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:0.679
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.111
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.567
When the network is plugged 0.038
And Tor is ready 19.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.483
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.686
Given I shutdown Tails and wait for the computer to power off 8.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.126
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.314
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.326
When the network is plugged 0.048
And Tor is ready 47.999
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.619
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.931
Given I shutdown Tails and wait for the computer to power off 4.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.626
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.878
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.383
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.035
And Tor is ready 46.677
Then the Upgrader considers the system as up-to-date 0.306
# 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.506
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.952
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
32.675
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.413
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.730
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 17.099
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.992
After features/support/hooks.rb:326 0.645
After features/support/hooks.rb:100 0.000