Project Number Date
test_Tails_ISO_stable 5135 03 Oct 2024, 08:48

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:19.855 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:12.112
Before features/support/hooks.rb:269 0.005
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 31.278
When I start Tails from USB drive "old" with network unplugged 1:34.008
Then the boot device has safe access rights 3.283
And Tails is running from USB drive "old" 1.347
And there is no persistence partition on USB drive "old" 0.131
And process "udev-watchdog" is running 0.159
And udev-watchdog is monitoring the correct device 0.381
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 8.941
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.122
Before features/support/hooks.rb:269 0.006
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:26.219
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 35.767
And I take note of which tps features are available 1.919
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 8.764
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.016
Tags: @product
3:5.208
Before features/support/hooks.rb:269 0.011
Given a computer 0.347
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.733
Then Tails is running from USB drive "old" 0.322
And all tps features are active 2.180
When I write some files expected to persist 3.368
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 3.403
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 6.454
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.187
After features/support/hooks.rb:326 0.099
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.461
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 11.353
And I log in to a new session 21.242
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.896
And I plug USB drive "to_upgrade" 2.477
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.250
Then the running Tails is installed on USB drive "to_upgrade" 18.645
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.367
After features/support/hooks.rb:326 7.103
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.759
Before features/support/hooks.rb:269 0.004
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.508
Then all tps features from the old Tails version are active 1.956
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.668
And the expected persistent files created with the old Tails version are present in the filesystem 1.602
And all persistent directories from the old Tails version have safe access rights 2.479
After features/support/hooks.rb:326 0.841
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:19.177
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 28.685
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.395
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.150
And Tor is ready 21.618
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.632
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.306
Given I shutdown Tails and wait for the computer to power off 11.588
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.453
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.932
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.359
# 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.439
When the network is plugged 0.080
And Tor is ready 19.724
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.465
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.938
Given I shutdown Tails and wait for the computer to power off 6.591
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.616
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.059
And the file system changes introduced in version 6.3~testoverlayfs are present 0.712
And only the 6.3~testoverlayfs SquashFS delta is installed 0.131
# 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.421
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.404
When the network is plugged 0.092
And Tor is ready 19.823
Then the Upgrader considers the system as up-to-date 0.352
# 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.473
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.149
After features/support/hooks.rb:326 0.830
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.014
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.884
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.408
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.937
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 17.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.401
After features/support/hooks.rb:326 0.869
After features/support/hooks.rb:100 0.000