Project Number Date
test_Tails_ISO_stable 5430 29 Jan 2025, 13:05

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:48.680 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:12.867
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.905
When I start Tails from USB drive "old" with network unplugged 1:35.547
Then the boot device has safe access rights 3.052
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 7.079
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.383
Before features/support/hooks.rb:269 0.003
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:29.570
Then Tails is running from USB drive "old" 0.446
And I create a persistent partition 31.849
And I take note of which tps features are available 2.032
Then a Tails persistence partition exists on USB drive "old" 0.845
And I shutdown Tails and wait for the computer to power off 6.448
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.862
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.596
Then Tails is running from USB drive "old" 1.176
And all tps features are active 2.030
When I write some files expected to persist 2.679
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.500
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 4.411
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.172
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:39.155
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.174
And I log in to a new session 19.269
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.607
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.040
Then the running Tails is installed on USB drive "to_upgrade" 21.245
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 2.612
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.458
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.825
Then all tps features from the old Tails version are active 2.522
And Tails is running from USB drive "to_upgrade" 0.486
And the boot device has safe access rights 3.863
And the expected persistent files created with the old Tails version are present in the filesystem 1.678
And all persistent directories from the old Tails version have safe access rights 2.892
After features/support/hooks.rb:326 0.628
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:38.247
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 13.126
And no SquashFS delta is installed 0.267
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.071
And Tor is ready 21.030
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.621
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.336
Given I shutdown Tails and wait for the computer to power off 9.143
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.276
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.128
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
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.308
# 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.283
When the network is plugged 0.064
And Tor is ready 18.052
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.705
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.978
Given I shutdown Tails and wait for the computer to power off 1:1.813
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.733
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.494
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.105
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.074
And Tor is ready 19.621
Then the Upgrader considers the system as up-to-date 0.313
# 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 14.847
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.008
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.705
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 10.260
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.616
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
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.086
And Tor is ready 18.852
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.741
After features/support/hooks.rb:326 0.637
After features/support/hooks.rb:100 0.000