Project Number Date
test_Tails_ISO_devel 3775 10 Apr 2025, 13:51

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 22:59.205 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:49.064
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.269
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 46.537
When I start Tails from USB drive "old" with network unplugged 1:55.407
Then the boot device has safe access rights 4.325
And Tails is running from USB drive "old" 0.446
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.429
And I unplug USB drive "old" 0.295
After features/support/hooks.rb:330 4.072
After features/support/hooks.rb:100 0.027
Tags: @product
2:29.525
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:40.840
Then Tails is running from USB drive "old" 0.393
And I create a persistent partition 34.794
And I take note of which tps features are available 2.876
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 9.458
After features/support/hooks.rb:330 0.282
After features/support/hooks.rb:100 0.013
Tags: @product
3:32.985
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.378
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:49.774
Then Tails is running from USB drive "old" 0.408
And all tps features are active 2.502
When I write some files expected to persist 2.224
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.279
And all persistence configuration files have safe access rights 0.505
And all persistent directories from the old Tails version have safe access rights 3.430
And I take note of which tps features are available 0.625
And I shutdown Tails and wait for the computer to power off 6.638
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.217
After features/support/hooks.rb:330 0.204
After features/support/hooks.rb:100 0.012
Tags: @product
3:7.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 24.517
And I log in to a new session 22.629
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.169
And I plug USB drive "to_upgrade" 2.522
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.470
Then the running Tails is installed on USB drive "to_upgrade" 31.688
And I unplug USB drive "to_upgrade" 0.498
And I unplug USB drive "__internal" 0.937
After features/support/hooks.rb:330 3.667
After features/support/hooks.rb:100 0.000
Tags: @product
2:40.684
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 1.473
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:26.779
Then all tps features from the old Tails version are active 2.909
And Tails is running from USB drive "to_upgrade" 0.448
And the boot device has safe access rights 4.036
And the expected persistent files created with the old Tails version are present in the filesystem 1.880
And all persistent directories from the old Tails version have safe access rights 3.154
After features/support/hooks.rb:330 1.833
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:12.018
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.514
And no SquashFS delta is installed 0.184
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.662
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.681
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.611
When the network is plugged 0.311
And Tor is ready 22.862
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.584
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.887
Given I shutdown Tails and wait for the computer to power off 11.539
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.898
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.422
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.286
# 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.294
When the network is plugged 0.083
And Tor is ready 19.619
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.333
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.068
Given I shutdown Tails and wait for the computer to power off 4.884
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.969
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.392
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.079
And Tor is ready 18.202
Then the Upgrader considers the system as up-to-date 0.322
# 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 17.636
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.045
After features/support/hooks.rb:330 0.727
After features/support/hooks.rb:100 0.050
Tags: @product @automatic_upgrade
1:7.491
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.628
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.534
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.153
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 51.009
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.996
After features/support/hooks.rb:330 1.092
After features/support/hooks.rb:100 0.000