Project Number Date
test_Tails_ISO_stable 5205 21 Oct 2024, 13: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:36.972 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:32.678
Before features/support/hooks.rb:269 0.005
Given a computer 0.239
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 37.938
When I start Tails from USB drive "old" with network unplugged 1:48.625
Then the boot device has safe access rights 3.622
And Tails is running from USB drive "old" 0.421
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.558
After features/support/hooks.rb:100 0.014
Tags: @product
2:21.364
Before features/support/hooks.rb:269 0.006
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login 1:36.603
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 32.992
And I take note of which tps features are available 1.848
Then a Tails persistence partition exists on USB drive "old" 0.849
And I shutdown Tails and wait for the computer to power off 8.457
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.010
Tags: @product
3:11.187
Before features/support/hooks.rb:269 0.007
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.773
Then Tails is running from USB drive "old" 0.875
And all tps features are active 4.660
When I write some files expected to persist 3.351
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.333
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 4.102
And I take note of which tps features are available 3.736
And I shutdown Tails and wait for the computer to power off 4.123
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.544
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
2:43.023
Before features/support/hooks.rb:269 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.497
And I log in to a new session 23.355
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.736
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.358
Then the running Tails is installed on USB drive "to_upgrade" 25.170
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.281
After features/support/hooks.rb:326 2.596
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.635
Before features/support/hooks.rb:269 0.009
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.856
Then all tps features from the old Tails version are active 1.828
And Tails is running from USB drive "to_upgrade" 0.436
And the boot device has safe access rights 4.150
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.665
After features/support/hooks.rb:326 0.729
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:49.261
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 26.689
And no SquashFS delta is installed 0.166
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.493
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.380
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.498
When the network is plugged 0.077
And Tor is ready 23.344
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.806
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.144
Given I shutdown Tails and wait for the computer to power off 8.982
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.024
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.204
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.473
# 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.318
When the network is plugged 0.066
And Tor is ready 22.581
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.489
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.467
Given I shutdown Tails and wait for the computer to power off 4.400
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.109
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.488
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.405
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.085
And Tor is ready 17.384
Then the Upgrader considers the system as up-to-date 0.370
# 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.251
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.190
After features/support/hooks.rb:326 0.772
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.821
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 9.736
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.651
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.842
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 22.250
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.199
After features/support/hooks.rb:326 0.700
After features/support/hooks.rb:100 0.000