Project Number Date
test_Tails_ISO_stable 5402 19 Jan 2025, 12:22

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:11.445 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:5.281
Before features/support/hooks.rb:269 0.005
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.600
When I start Tails from USB drive "old" with network unplugged 1:30.344
Then the boot device has safe access rights 2.984
And Tails is running from USB drive "old" 0.443
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.509
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.490
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:21.641
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 32.016
And I take note of which tps features are available 1.417
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 8.097
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.896
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.826
Then Tails is running from USB drive "old" 0.575
And all tps features are active 2.097
When I write some files expected to persist 1.888
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.290
And all persistence configuration files have safe access rights 0.607
And all persistent directories from the old Tails version have safe access rights 2.315
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.382
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.283
After features/support/hooks.rb:326 0.094
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.475
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.903
And I log in to a new session 17.152
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.441
And I plug USB drive "to_upgrade" 2.357
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.672
Then the running Tails is installed on USB drive "to_upgrade" 20.482
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.247
After features/support/hooks.rb:326 2.389
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.915
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.752
Then all tps features from the old Tails version are active 1.623
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.033
And the expected persistent files created with the old Tails version are present in the filesystem 1.641
And all persistent directories from the old Tails version have safe access rights 2.366
After features/support/hooks.rb:326 0.644
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:36.201
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.697
And no SquashFS delta is installed 0.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.561
When the network is plugged 0.074
And Tor is ready 23.545
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.803
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.759
Given I shutdown Tails and wait for the computer to power off 10.728
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.666
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.228
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.267
When the network is plugged 0.092
And Tor is ready 19.563
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.028
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.908
Given I shutdown Tails and wait for the computer to power off 4.261
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.651
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.389
And the file system changes introduced in version 6.3~testoverlayfs are present 0.438
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.078
And Tor is ready 46.112
Then the Upgrader considers the system as up-to-date 0.288
# 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.648
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.167
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
52.184
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.410
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.470
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 21.801
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.308
After features/support/hooks.rb:326 0.657
After features/support/hooks.rb:100 0.000