Project Number Date
test_Tails_ISO_devel 3780 12 Apr 2025, 13:08

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:49.970 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:14.046
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 34.939
When I start Tails from USB drive "old" with network unplugged 1:33.545
Then the boot device has safe access rights 3.176
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.366
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 1.112
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.812
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:32.817
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 34.218
And I take note of which tps features are available 1.901
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 8.484
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.401
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.423
Then Tails is running from USB drive "old" 0.335
And all tps features are active 2.055
When I write some files expected to persist 1.833
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.356
And I take note of which tps features are available 0.679
And I shutdown Tails and wait for the computer to power off 5.501
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.375
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.712
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 11.262
And I log in to a new session 19.962
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.771
And I plug USB drive "to_upgrade" 2.751
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.869
Then the running Tails is installed on USB drive "to_upgrade" 28.583
And I unplug USB drive "to_upgrade" 0.267
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:330 6.860
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.890
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.563
Then all tps features from the old Tails version are active 1.833
And Tails is running from USB drive "to_upgrade" 0.394
And the boot device has safe access rights 3.756
And the expected persistent files created with the old Tails version are present in the filesystem 1.655
And all persistent directories from the old Tails version have safe access rights 2.491
After features/support/hooks.rb:330 1.429
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:51.285
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 with a persistent partition enabled and logged in 11.623
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.484
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.677
When the network is plugged 0.107
And Tor is ready 22.925
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.965
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.676
Given I shutdown Tails and wait for the computer to power off 11.205
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.158
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.116
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.260
When the network is plugged 0.079
And Tor is ready 20.618
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.628
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.038
Given I shutdown Tails and wait for the computer to power off 4.462
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.313
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.172
And the file system changes introduced in version 6.3~testoverlayfs are present 0.550
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.082
And Tor is ready 15.246
Then the Upgrader considers the system as up-to-date 10.981
# 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.484
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.588
After features/support/hooks.rb:330 0.846
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
36.819
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 with a persistent partition enabled and logged in 9.808
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 17.742
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.681
After features/support/hooks.rb:330 1.196
After features/support/hooks.rb:100 0.000