Project Number Date
test_Tails_ISO_stable 5463 17 Feb 2025, 13:13

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 21:36.476 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:34.074
Before features/support/hooks.rb:269 0.008
Given a computer 0.255
And I create a 7200 MiB disk named "old" 0.071
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 1:3.945
When I start Tails from USB drive "old" with network unplugged 1:24.539
Then the boot device has safe access rights 3.122
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 3.778
After features/support/hooks.rb:100 0.011
Tags: @product
2:18.420
Before features/support/hooks.rb:269 0.008
Given a computer 0.294
And I start Tails from USB drive "old" with network unplugged and I login 1:32.814
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 33.359
And I take note of which tps features are available 1.764
Then a Tails persistence partition exists on USB drive "old" 0.828
And I shutdown Tails and wait for the computer to power off 9.006
After features/support/hooks.rb:326 0.300
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.082
Before features/support/hooks.rb:269 0.006
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.378
Then Tails is running from USB drive "old" 0.821
And all tps features are active 2.554
When I write some files expected to persist 2.014
# 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.489
And all persistent directories from the old Tails version have safe access rights 3.188
And I take note of which tps features are available 0.665
And I shutdown Tails and wait for the computer to power off 4.157
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.274
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.012
Tags: @product
2:44.335
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 20.626
And I log in to a new session 18.571
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.556
And I plug USB drive "to_upgrade" 2.529
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.677
Then the running Tails is installed on USB drive "to_upgrade" 20.652
And I unplug USB drive "to_upgrade" 0.342
And I unplug USB drive "__internal" 0.379
After features/support/hooks.rb:326 3.778
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.852
Before features/support/hooks.rb:269 0.007
Given a computer 1.414
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.380
Then all tps features from the old Tails version are active 1.816
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.292
And the expected persistent files created with the old Tails version are present in the filesystem 1.864
And all persistent directories from the old Tails version have safe access rights 2.716
After features/support/hooks.rb:326 0.921
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:44.602
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 24.958
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.504
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.683
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.628
When the network is plugged 0.108
And Tor is ready 24.183
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.598
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.681
Given I shutdown Tails and wait for the computer to power off 11.098
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.782
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.750
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.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.434
When the network is plugged 0.101
And Tor is ready 19.757
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.705
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.979
Given I shutdown Tails and wait for the computer to power off 6.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.649
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.873
And the file system changes introduced in version 6.3~testoverlayfs are present 0.600
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.429
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.096
And Tor is ready 21.259
Then the Upgrader considers the system as up-to-date 0.333
# 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 16.226
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.164
After features/support/hooks.rb:326 0.770
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
43.109
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 15.227
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.473
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.203
And Tor is ready 21.148
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.923
After features/support/hooks.rb:326 1.581
After features/support/hooks.rb:100 0.000