Project Number Date
test_Tails_ISO_stable 5204 21 Oct 2024, 12:23

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:36.967 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:20.831
Before features/support/hooks.rb:269 0.004
Given a computer 0.323
And I create a 7200 MiB disk named "old" 0.109
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 32.452
When I start Tails from USB drive "old" with network unplugged 1:42.504
Then the boot device has safe access rights 3.315
And Tails is running from USB drive "old" 0.384
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 3.506
After features/support/hooks.rb:100 0.044
Tags: @product
2:14.742
Before features/support/hooks.rb:269 0.012
Given a computer 0.267
And I start Tails from USB drive "old" with network unplugged and I login 1:28.463
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 35.078
And I take note of which tps features are available 1.343
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.384
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.067
Before features/support/hooks.rb:269 0.004
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.617
Then Tails is running from USB drive "old" 1.812
And all tps features are active 1.948
When I write some files expected to persist 3.299
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 3.345
And I take note of which tps features are available 0.656
And I shutdown Tails and wait for the computer to power off 4.341
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.229
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.410
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 13.549
And I log in to a new session 20.715
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.201
And I plug USB drive "to_upgrade" 2.350
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.199
Then the running Tails is installed on USB drive "to_upgrade" 21.979
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.558
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.042
Before features/support/hooks.rb:269 0.007
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.341
Then all tps features from the old Tails version are active 1.757
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.190
And the expected persistent files created with the old Tails version are present in the filesystem 1.772
And all persistent directories from the old Tails version have safe access rights 2.431
After features/support/hooks.rb:326 0.909
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:35.194
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.008
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.335
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.517
When the network is plugged 0.064
And Tor is ready 26.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.011
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.713
Given I shutdown Tails and wait for the computer to power off 8.740
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.297
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.075
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
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.322
# 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.273
When the network is plugged 0.072
And Tor is ready 23.017
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.099
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.021
Given I shutdown Tails and wait for the computer to power off 4.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.388
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.573
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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.081
And Tor is ready 18.029
Then the Upgrader considers the system as up-to-date 0.358
# 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.836
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.939
After features/support/hooks.rb:326 0.696
After features/support/hooks.rb:100 0.075
Tags: @product @automatic_upgrade
38.678
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.186
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.370
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.812
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 20.510
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.673
After features/support/hooks.rb:326 0.719
After features/support/hooks.rb:100 0.000