Project Number Date
test_Tails_ISO_devel 3741 17 Mar 2025, 13:27

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:10.438 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:15.573
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.398
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 31.419
When I start Tails from USB drive "old" with network unplugged 1:38.289
Then the boot device has safe access rights 3.183
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.384
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:330 9.954
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:24.037
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 35.269
And I take note of which tps features are available 1.763
Then a Tails persistence partition exists on USB drive "old" 0.872
And I shutdown Tails and wait for the computer to power off 8.284
After features/support/hooks.rb:330 0.139
After features/support/hooks.rb:100 0.008
Tags: @product
3:2.723
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.715
Then Tails is running from USB drive "old" 0.339
And all tps features are active 2.790
When I write some files expected to persist 1.895
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 2.631
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 4.508
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.419
After features/support/hooks.rb:330 0.141
After features/support/hooks.rb:100 0.011
Tags: @product
2:32.681
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.642
And I log in to a new session 19.995
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.583
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.550
Then the running Tails is installed on USB drive "to_upgrade" 19.968
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 1.825
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.022
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.077
Then all tps features from the old Tails version are active 1.769
And Tails is running from USB drive "to_upgrade" 0.397
And the boot device has safe access rights 3.269
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 2.679
After features/support/hooks.rb:330 1.697
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:6.423
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.777
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.426
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.140
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.540
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.098
And Tor is ready 20.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.791
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.405
Given I shutdown Tails and wait for the computer to power off 8.973
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.331
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.278
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.108
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.281
When the network is plugged 0.066
And Tor is ready 20.783
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.516
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.474
Given I shutdown Tails and wait for the computer to power off 4.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.123
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.360
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.120
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.501
When the network is plugged 0.129
And Tor is ready 21.216
Then the Upgrader considers the system as up-to-date 0.377
# 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.929
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.703
After features/support/hooks.rb:330 0.842
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
39.240
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.128
But a current signing key is available on our website 0.000
When the network is plugged 0.112
And Tor is ready 21.948
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.400
After features/support/hooks.rb:330 1.247
After features/support/hooks.rb:100 0.000