Project Number Date
test_Tails_ISO_stable 4769 04 Apr 2024, 18:15

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 17:42.302 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
1:42.966
Before features/support/hooks.rb:245 0.007
Given a computer 0.378
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 24.185
When I start Tails from USB drive "old" with network unplugged 1:13.018
Then the boot device has safe access rights 3.263
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:291 3.591
After features/support/hooks.rb:75 0.009
Tags: @product
2:0.411
Before features/support/hooks.rb:245 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:17.875
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 30.772
And I take note of which tps features are available 1.850
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.586
After features/support/hooks.rb:291 0.185
After features/support/hooks.rb:75 0.008
Tags: @product
2:29.985
Before features/support/hooks.rb:245 0.004
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.521
Then Tails is running from USB drive "old" 0.365
And all tps features are active 1.968
When I write some files expected to persist 1.779
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.757
And I take note of which tps features are available 0.481
And I shutdown Tails and wait for the computer to power off 4.150
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.118
After features/support/hooks.rb:291 0.160
After features/support/hooks.rb:75 0.011
Tags: @product
2:25.279
Before features/support/hooks.rb:245 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.016
And I log in to a new session 19.361
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.431
And I plug USB drive "to_upgrade" 2.473
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.344
Then the running Tails is installed on USB drive "to_upgrade" 15.254
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:291 2.416
After features/support/hooks.rb:75 0.000
Tags: @product
2:9.925
Before features/support/hooks.rb:245 0.006
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.766
Then all tps features from the old Tails version are active 1.712
And Tails is running from USB drive "to_upgrade" 0.414
And the boot device has safe access rights 3.617
And the expected persistent files created with the old Tails version are present in the filesystem 1.596
And all persistent directories from the old Tails version have safe access rights 2.608
After features/support/hooks.rb:291 0.816
After features/support/hooks.rb:75 0.011
5:58.129
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.121
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.386
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.035
And Tor is ready 17.875
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.193
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.898
Given I shutdown Tails and wait for the computer to power off 6.897
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.126
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.112
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.237
When the network is plugged 0.047
And Tor is ready 15.749
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.814
Given I shutdown Tails and wait for the computer to power off 4.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.957
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.014
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.272
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.050
And Tor is ready 18.448
Then the Upgrader considers the system as up-to-date 0.264
# 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.590
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.869
After features/support/hooks.rb:291 0.774
After features/support/hooks.rb:75 0.018
55.603
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.007
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.636
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 44.840
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.663
After features/support/hooks.rb:291 0.628
After features/support/hooks.rb:75 0.000