Project Number Date
test_Tails_ISO_devel 3765 03 Apr 2025, 22:07

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:55.005 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.916
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 31.303
When I start Tails from USB drive "old" with network unplugged 1:36.377
Then the boot device has safe access rights 2.960
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:330 6.868
After features/support/hooks.rb:100 0.012
Tags: @product
2:23.175
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:38.590
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 32.405
And I take note of which tps features are available 2.255
Then a Tails persistence partition exists on USB drive "old" 0.852
And I shutdown Tails and wait for the computer to power off 8.491
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.068
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.801
Then Tails is running from USB drive "old" 1.137
And all tps features are active 2.029
When I write some files expected to persist 2.821
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 4.543
And I take note of which tps features are available 0.473
And I shutdown Tails and wait for the computer to power off 4.370
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.061
After features/support/hooks.rb:330 0.136
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.418
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 11.169
And I log in to a new session 16.988
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.803
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.374
Then the running Tails is installed on USB drive "to_upgrade" 22.291
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 0.853
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.329
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.654
Then all tps features from the old Tails version are active 1.750
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.452
And the expected persistent files created with the old Tails version are present in the filesystem 1.446
And all persistent directories from the old Tails version have safe access rights 2.463
After features/support/hooks.rb:330 1.470
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:52.222
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.549
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.768
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.088
When the network is plugged 0.138
And Tor is ready 22.405
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.086
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.883
Given I shutdown Tails and wait for the computer to power off 8.790
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.935
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.097
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.296
When the network is plugged 0.060
And Tor is ready 15.995
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.161
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.779
Given I shutdown Tails and wait for the computer to power off 4.359
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.110
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 3.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.472
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.361
When the network is plugged 0.070
And Tor is ready 18.319
Then the Upgrader considers the system as up-to-date 0.325
# 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.170
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.467
After features/support/hooks.rb:330 0.669
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.874
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 with a persistent partition enabled and logged in 10.725
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.530
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.099
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 18.149
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.210
After features/support/hooks.rb:330 0.871
After features/support/hooks.rb:100 0.000