Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 4 16 Apr 2025, 21:02

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:58.153 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:41.840
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.249
And I create a 7200 MiB disk named "old" 0.076
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 1:3.179
When I start Tails from USB drive "old" with network unplugged 1:32.682
Then the boot device has safe access rights 3.385
And Tails is running from USB drive "old" 0.532
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 3.569
After features/support/hooks.rb:100 0.024
Tags: @product
2:13.323
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:28.277
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 32.645
And I take note of which tps features are available 2.301
Then a Tails persistence partition exists on USB drive "old" 0.822
And I shutdown Tails and wait for the computer to power off 8.659
After features/support/hooks.rb:330 0.188
After features/support/hooks.rb:100 0.012
Tags: @product
3:3.878
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.288
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.591
Then Tails is running from USB drive "old" 1.129
And all tps features are active 3.546
When I write some files expected to persist 3.182
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.443
And all persistent directories from the old Tails version have safe access rights 2.672
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 6.568
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.738
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.013
Tags: @product
2:31.312
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 13.120
And I log in to a new session 18.332
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.675
And I plug USB drive "to_upgrade" 2.439
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.207
Then the running Tails is installed on USB drive "to_upgrade" 21.114
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:330 2.200
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.708
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.185
Then all tps features from the old Tails version are active 1.734
And Tails is running from USB drive "to_upgrade" 0.302
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.484
And all persistent directories from the old Tails version have safe access rights 2.511
After features/support/hooks.rb:330 1.326
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:25.549
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.643
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.401
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.081
And Tor is ready 18.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.401
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.437
Given I shutdown Tails and wait for the computer to power off 9.026
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.682
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.378
And the file system changes introduced in version 6.2~testoverlayfs are present 0.364
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.307
When the network is plugged 0.069
And Tor is ready 47.455
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.594
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.896
Given I shutdown Tails and wait for the computer to power off 4.445
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.096
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.056
And the file system changes introduced in version 6.3~testoverlayfs are present 0.674
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.476
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.093
And Tor is ready 48.569
Then the Upgrader considers the system as up-to-date 0.316
# 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.694
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.073
After features/support/hooks.rb:330 0.729
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.539
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.721
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.714
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.148
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 17.433
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.355
After features/support/hooks.rb:330 0.697
After features/support/hooks.rb:100 0.000