Project Number Date
test_Tails_ISO_devel 3811 14 May 2025, 13:11

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:22.909 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:35.142
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 31.522
When I start Tails from USB drive "old" with network unplugged 1:57.584
Then the boot device has safe access rights 3.497
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.124
And udev-watchdog is monitoring the correct device 0.375
And I unplug USB drive "old" 0.249
After features/support/hooks.rb:330 7.339
After features/support/hooks.rb:100 0.019
Tags: @product
2:24.470
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:37.358
Then Tails is running from USB drive "old" 0.446
And I create a persistent partition 32.035
And I take note of which tps features are available 4.542
Then a Tails persistence partition exists on USB drive "old" 0.895
And I shutdown Tails and wait for the computer to power off 8.969
After features/support/hooks.rb:330 0.257
After features/support/hooks.rb:100 0.012
Tags: @product
3:7.798
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.411
Then Tails is running from USB drive "old" 0.679
And all tps features are active 2.543
When I write some files expected to persist 2.019
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.277
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 4.496
And I take note of which tps features are available 0.592
And I shutdown Tails and wait for the computer to power off 6.852
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.304
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.334
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 12.695
And I log in to a new session 19.545
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.636
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.799
Then the running Tails is installed on USB drive "to_upgrade" 22.803
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 2.457
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.878
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.999
Then all tps features from the old Tails version are active 1.822
And Tails is running from USB drive "to_upgrade" 0.393
And the boot device has safe access rights 4.080
And the expected persistent files created with the old Tails version are present in the filesystem 1.580
And all persistent directories from the old Tails version have safe access rights 2.774
After features/support/hooks.rb:330 1.346
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
7:13.219
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.979
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.502
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.132
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.366
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.524
When the network is plugged 0.081
And Tor is ready 23.504
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.089
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.578
Given I shutdown Tails and wait for the computer to power off 10.527
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.748
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.719
And the file system changes introduced in version 6.2~testoverlayfs are present 0.478
And only the 6.2~testoverlayfs SquashFS delta is installed 0.111
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.376
# 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.354
When the network is plugged 0.078
And Tor is ready 21.865
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.048
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.875
Given I shutdown Tails and wait for the computer to power off 6.493
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.631
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 5.893
And the file system changes introduced in version 6.3~testoverlayfs are present 0.617
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.587
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.663
When the network is plugged 0.087
And Tor is ready 19.798
Then the Upgrader considers the system as up-to-date 0.341
# 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.566
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.366
After features/support/hooks.rb:330 0.913
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
59.065
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 10.610
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.416
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.115
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 47.117
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.665
After features/support/hooks.rb:330 0.924
After features/support/hooks.rb:100 0.000