Project Number Date
test_Tails_ISO_devel 3407 31 May 2024, 02:36

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 20:18.226 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:7.037
Before features/support/hooks.rb:265 0.010
Given a computer 0.237
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 28.856
When I start Tails from USB drive "old" with network unplugged 1:32.597
Then the boot device has safe access rights 3.227
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:311 9.031
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.055
Before features/support/hooks.rb:265 0.008
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login 1:28.749
Then Tails is running from USB drive "old" 0.407
And I create a persistent partition 38.457
And I take note of which tps features are available 1.983
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.382
After features/support/hooks.rb:311 0.310
After features/support/hooks.rb:100 0.010
Tags: @product
2:47.514
Before features/support/hooks.rb:265 0.008
Given a computer 0.614
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.152
Then Tails is running from USB drive "old" 0.460
And all tps features are active 2.153
When I write some files expected to persist 1.936
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.559
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 4.463
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.014
After features/support/hooks.rb:311 0.168
After features/support/hooks.rb:100 0.011
Tags: @product
2:32.009
Before features/support/hooks.rb:265 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 11.991
And I log in to a new session 20.972
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.497
And I plug USB drive "to_upgrade" 2.505
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.295
Then the running Tails is installed on USB drive "to_upgrade" 18.310
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:311 3.951
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.526
Before features/support/hooks.rb:265 0.023
Given a computer 0.344
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.114
Then all tps features from the old Tails version are active 1.761
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.316
And the expected persistent files created with the old Tails version are present in the filesystem 1.383
And all persistent directories from the old Tails version have safe access rights 2.282
After features/support/hooks.rb:311 0.711
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:29.573
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.370
And no SquashFS delta is installed 0.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.133
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.353
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.041
And Tor is ready 50.057
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.633
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.044
Given I shutdown Tails and wait for the computer to power off 9.272
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.135
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.298
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.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.426
# 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.037
And Tor is ready 19.649
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.355
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.416
Given I shutdown Tails and wait for the computer to power off 4.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.697
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.878
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.346
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.046
And Tor is ready 18.340
Then the Upgrader considers the system as up-to-date 0.380
# 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.655
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.017
After features/support/hooks.rb:311 0.758
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
38.510
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.634
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 1.026
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 20.996
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.516
After features/support/hooks.rb:311 0.715
After features/support/hooks.rb:100 0.000