Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 14 25 Apr 2025, 23:18

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:50.451 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:36.678
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.099
And I write an old version of the Tails USB image to disk "old" 1:10.324
When I start Tails from USB drive "old" with network unplugged 1:20.788
Then the boot device has safe access rights 3.104
And Tails is running from USB drive "old" 0.396
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:330 3.580
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.223
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:27.634
Then Tails is running from USB drive "old" 0.378
And I create a persistent partition 31.241
And I take note of which tps features are available 3.177
Then a Tails persistence partition exists on USB drive "old" 0.856
And I shutdown Tails and wait for the computer to power off 6.693
After features/support/hooks.rb:330 0.166
After features/support/hooks.rb:100 0.011
Tags: @product
2:48.242
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.092
Then Tails is running from USB drive "old" 0.550
And all tps features are active 2.231
When I write some files expected to persist 1.797
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.599
And all persistent directories from the old Tails version have safe access rights 2.548
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 4.384
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.086
After features/support/hooks.rb:330 0.104
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.210
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 9.922
And I log in to a new session 17.990
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.619
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.002
Then the running Tails is installed on USB drive "to_upgrade" 19.885
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 0.879
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.926
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.613
Then all tps features from the old Tails version are active 1.578
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.454
And the expected persistent files created with the old Tails version are present in the filesystem 1.323
And all persistent directories from the old Tails version have safe access rights 2.456
After features/support/hooks.rb:330 1.350
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
8:54.745
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.792
And no SquashFS delta is installed 0.136
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.828
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.179
And Tor is ready 21.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.298
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.820
Given I shutdown Tails and wait for the computer to power off 1:18.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.714
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.252
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.120
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.421
# 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.420
When the network is plugged 0.097
And Tor is ready 19.314
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.197
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.161
Given I shutdown Tails and wait for the computer to power off 1:4.890
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.420
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.062
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.388
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.072
And Tor is ready 18.665
Then the Upgrader considers the system as up-to-date 10.878
# 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.270
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.431
After features/support/hooks.rb:330 0.703
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.424
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.622
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.130
And the signing key used by the Upgrader is outdated 0.145
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 18.343
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.652
After features/support/hooks.rb:330 1.890
After features/support/hooks.rb:100 0.000