Project Number Date
test_Tails_ISO_devel 3487 20 Aug 2024, 12:45

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:10.802 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:25.021
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.647
When I start Tails from USB drive "old" with network unplugged 1:45.947
Then the boot device has safe access rights 3.809
And Tails is running from USB drive "old" 0.507
And there is no persistence partition on USB drive "old" 0.092
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.243
After features/support/hooks.rb:326 8.925
After features/support/hooks.rb:100 0.013
Tags: @product
2:13.468
Before features/support/hooks.rb:269 0.009
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:29.971
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 31.702
And I take note of which tps features are available 1.743
Then a Tails persistence partition exists on USB drive "old" 0.946
And I shutdown Tails and wait for the computer to power off 8.489
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.174
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.814
Then Tails is running from USB drive "old" 0.428
And all tps features are active 2.172
When I write some files expected to persist 1.785
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.835
And I take note of which tps features are available 0.513
And I shutdown Tails and wait for the computer to power off 4.431
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.359
After features/support/hooks.rb:326 0.097
After features/support/hooks.rb:100 0.012
Tags: @product
2:33.493
Before features/support/hooks.rb:269 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 11.251
And I log in to a new session 18.126
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.023
And I plug USB drive "to_upgrade" 2.517
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.627
Then the running Tails is installed on USB drive "to_upgrade" 22.467
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:326 3.006
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.771
Before features/support/hooks.rb:269 0.005
Given a computer 0.242
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.459
Then all tps features from the old Tails version are active 1.877
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 4.106
And the expected persistent files created with the old Tails version are present in the filesystem 1.800
And all persistent directories from the old Tails version have safe access rights 2.938
After features/support/hooks.rb:326 1.218
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
6:57.609
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.388
And no SquashFS delta is installed 0.251
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.958
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.499
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.069
And Tor is ready 20.218
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.909
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.281
Given I shutdown Tails and wait for the computer to power off 11.097
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.465
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.352
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.391
# 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.346
When the network is plugged 0.084
And Tor is ready 18.824
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.490
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.074
Given I shutdown Tails and wait for the computer to power off 4.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.115
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.347
And the file system changes introduced in version 6.3~testoverlayfs are present 0.649
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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.082
And Tor is ready 18.800
Then the Upgrader considers the system as up-to-date 0.351
# 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.262
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.173
After features/support/hooks.rb:326 0.818
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
38.264
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 9.823
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.664
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.784
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 19.865
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.985
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.000