Project Number Date
test_Tails_ISO_devel 3414 04 Jun 2024, 12:58

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:44.875 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:8.097
Before features/support/hooks.rb:265 0.008
Given a computer 0.245
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 32.475
When I start Tails from USB drive "old" with network unplugged 1:30.243
Then the boot device has safe access rights 3.055
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:311 3.754
After features/support/hooks.rb:100 0.014
Tags: @product
2:15.816
Before features/support/hooks.rb:265 0.009
Given a computer 0.269
And I start Tails from USB drive "old" with network unplugged and I login 1:27.324
Then Tails is running from USB drive "old" 0.428
And I create a persistent partition 36.829
And I take note of which tps features are available 1.583
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 8.603
After features/support/hooks.rb:311 0.184
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.930
Before features/support/hooks.rb:265 0.006
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.190
Then Tails is running from USB drive "old" 0.530
And all tps features are active 4.008
When I write some files expected to persist 2.014
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.325
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 2.929
And I take note of which tps features are available 0.658
And I shutdown Tails and wait for the computer to power off 4.568
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.046
After features/support/hooks.rb:311 0.208
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.298
Before features/support/hooks.rb:265 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 12.971
And I log in to a new session 20.354
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.836
And I plug USB drive "to_upgrade" 2.930
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.077
Then the running Tails is installed on USB drive "to_upgrade" 21.730
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:311 1.844
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.110
Before features/support/hooks.rb:265 0.009
Given a computer 0.245
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.247
Then all tps features from the old Tails version are active 1.896
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.152
And the expected persistent files created with the old Tails version are present in the filesystem 1.668
And all persistent directories from the old Tails version have safe access rights 2.591
After features/support/hooks.rb:311 0.712
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:45.232
Before features/support/hooks.rb:265 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.841
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
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.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.219
And Tor is ready 50.588
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.593
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.090
Given I shutdown Tails and wait for the computer to power off 9.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.971
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 3.107
And the file system changes introduced in version 6.2~testoverlayfs are present 0.483
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.553
# 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.299
When the network is plugged 0.064
And Tor is ready 20.280
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.801
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.438
Given I shutdown Tails and wait for the computer to power off 9.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.060
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.314
And the file system changes introduced in version 6.3~testoverlayfs are present 0.472
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.355
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.056
And Tor is ready 20.771
Then the Upgrader considers the system as up-to-date 0.379
# 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.929
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.101
After features/support/hooks.rb:311 0.798
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
38.390
Before features/support/hooks.rb:265 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.851
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 1.156
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 17.834
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.972
After features/support/hooks.rb:311 0.928
After features/support/hooks.rb:100 0.000