Project Number Date
test_Tails_ISO_devel 3561 25 Oct 2024, 12:42

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 19:42.790 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:21.822
Before features/support/hooks.rb:269 0.007
Given a computer 0.255
And I create a 7200 MiB disk named "old" 0.074
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 44.011
When I start Tails from USB drive "old" with network unplugged 1:32.284
Then the boot device has safe access rights 3.052
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:326 7.117
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.596
Before features/support/hooks.rb:269 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:22.295
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 31.361
And I take note of which tps features are available 1.378
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 8.194
After features/support/hooks.rb:326 0.207
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.410
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:8.760
Then Tails is running from USB drive "old" 1.024
And all tps features are active 2.474
When I write some files expected to persist 2.172
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.781
And all persistence configuration files have safe access rights 0.408
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.436
And I shutdown Tails and wait for the computer to power off 4.530
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.782
After features/support/hooks.rb:326 0.115
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.702
Before features/support/hooks.rb:269 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.280
And I log in to a new session 19.975
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.707
And I plug USB drive "to_upgrade" 2.388
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.413
Then the running Tails is installed on USB drive "to_upgrade" 23.440
And I unplug USB drive "to_upgrade" 0.273
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 2.752
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.563
Before features/support/hooks.rb:269 0.005
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.479
Then all tps features from the old Tails version are active 1.737
And Tails is running from USB drive "to_upgrade" 0.452
And the boot device has safe access rights 3.557
And the expected persistent files created with the old Tails version are present in the filesystem 1.467
And all persistent directories from the old Tails version have safe access rights 2.662
After features/support/hooks.rb:326 1.032
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:49.499
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 14.374
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.354
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.090
And Tor is ready 30.551
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.831
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.032
Given I shutdown Tails and wait for the computer to power off 11.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.275
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.337
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.472
# 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.085
And Tor is ready 19.739
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.396
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.352
Given I shutdown Tails and wait for the computer to power off 4.460
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.542
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.246
And the file system changes introduced in version 6.3~testoverlayfs are present 0.603
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.416
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.317
When the network is plugged 0.087
And Tor is ready 20.738
Then the Upgrader considers the system as up-to-date 0.403
# 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.431
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.044
After features/support/hooks.rb:326 0.717
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
43.194
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 14.746
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.897
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 23.064
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.031
After features/support/hooks.rb:326 0.890
After features/support/hooks.rb:100 0.000