Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 6 17 Apr 2025, 21: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 19:19.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:3.908
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.871
When I start Tails from USB drive "old" with network unplugged 1:27.487
Then the boot device has safe access rights 3.262
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.230
After features/support/hooks.rb:330 7.102
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.345
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:30.459
Then Tails is running from USB drive "old" 0.399
And I create a persistent partition 31.526
And I take note of which tps features are available 2.345
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.581
After features/support/hooks.rb:330 0.189
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.191
Then Tails is running from USB drive "old" 0.803
And all tps features are active 1.978
When I write some files expected to persist 1.796
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.490
And all persistent directories from the old Tails version have safe access rights 3.005
And I take note of which tps features are available 0.805
And I shutdown Tails and wait for the computer to power off 6.405
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.921
After features/support/hooks.rb:330 0.140
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.635
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.919
And I log in to a new session 18.952
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.746
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.320
Then the running Tails is installed on USB drive "to_upgrade" 19.841
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:330 1.173
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.737
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.263
Then all tps features from the old Tails version are active 1.567
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.636
And the expected persistent files created with the old Tails version are present in the filesystem 1.447
And all persistent directories from the old Tails version have safe access rights 2.320
After features/support/hooks.rb:330 1.267
After features/support/hooks.rb:100 0.008
6:43.820
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 10.678
And no SquashFS delta is installed 0.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.448
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.074
And Tor is ready 24.211
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.286
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.819
Given I shutdown Tails and wait for the computer to power off 8.688
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.511
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.238
And the file system changes introduced in version 6.2~testoverlayfs are present 0.428
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.335
When the network is plugged 0.071
And Tor is ready 20.043
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.215
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.743
Given I shutdown Tails and wait for the computer to power off 4.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.107
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.363
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
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.297
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.067
And Tor is ready 20.721
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 15.662
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.728
After features/support/hooks.rb:330 0.732
After features/support/hooks.rb:100 0.018
38.161
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.484
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.111
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 19.300
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.690
After features/support/hooks.rb:330 2.598
After features/support/hooks.rb:100 0.000