Project Number Date
test_Tails_ISO_stable 5274 17 Nov 2024, 09:00

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:48.052 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:4.151
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 32.136
When I start Tails from USB drive "old" with network unplugged 1:26.399
Then the boot device has safe access rights 3.250
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:326 9.298
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.629
Before features/support/hooks.rb:269 0.004
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:26.676
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 32.966
And I take note of which tps features are available 4.244
Then a Tails persistence partition exists on USB drive "old" 0.871
And I shutdown Tails and wait for the computer to power off 8.296
After features/support/hooks.rb:326 0.204
After features/support/hooks.rb:100 0.007
Tags: @product
2:56.154
Before features/support/hooks.rb:269 0.005
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.826
Then Tails is running from USB drive "old" 1.022
And all tps features are active 2.365
When I write some files expected to persist 1.988
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.324
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 2.629
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 4.361
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.539
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.008
Tags: @product
2:46.403
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 18.838
And I log in to a new session 22.097
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.858
And I plug USB drive "to_upgrade" 2.594
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.269
Then the running Tails is installed on USB drive "to_upgrade" 24.242
And I unplug USB drive "to_upgrade" 0.272
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:326 3.559
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.247
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.497
Then all tps features from the old Tails version are active 1.950
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.294
And the expected persistent files created with the old Tails version are present in the filesystem 1.394
And all persistent directories from the old Tails version have safe access rights 2.557
After features/support/hooks.rb:326 1.142
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:48.848
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 17.648
And no SquashFS delta is installed 0.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.621
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.113
And Tor is ready 19.947
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.616
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.951
Given I shutdown Tails and wait for the computer to power off 10.705
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.668
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 2.394
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.413
# 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.366
When the network is plugged 0.071
And Tor is ready 20.557
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.089
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.311
Given I shutdown Tails and wait for the computer to power off 6.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.263
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.216
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.398
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.062
And Tor is ready 19.679
Then the Upgrader considers the system as up-to-date 0.308
# 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.683
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.894
After features/support/hooks.rb:326 0.673
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.617
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.035
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.771
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 18.929
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.387
After features/support/hooks.rb:326 1.050
After features/support/hooks.rb:100 0.000