Project Number Date
test_Tails_ISO_stable 5704 10 Jun 2025, 13:15

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 22:4.390 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:39.151
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 35.100
When I start Tails from USB drive "old" with network unplugged 1:57.739
Then the boot device has safe access rights 3.771
And Tails is running from USB drive "old" 0.408
And there is no persistence partition on USB drive "old" 0.096
And process "udev-watchdog" is running 0.136
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.248
After features/support/hooks.rb:330 3.570
After features/support/hooks.rb:100 0.044
Tags: @product
2:21.630
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:35.160
Then Tails is running from USB drive "old" 0.449
And I create a persistent partition 33.894
And I take note of which tps features are available 2.507
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 8.503
After features/support/hooks.rb:330 0.191
After features/support/hooks.rb:100 0.009
Tags: @product
3:11.255
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.966
Then Tails is running from USB drive "old" 0.395
And all tps features are active 2.222
When I write some files expected to persist 1.715
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.422
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.279
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.902
After features/support/hooks.rb:330 0.259
After features/support/hooks.rb:100 0.011
Tags: @product
2:46.749
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 without a persistent partition and stopped at Tails Greeter's login screen 11.847
And I log in to a new session 22.369
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.528
And I plug USB drive "to_upgrade" 3.096
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.602
Then the running Tails is installed on USB drive "to_upgrade" 26.817
And I unplug USB drive "to_upgrade" 0.272
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:330 1.987
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.810
Then all tps features from the old Tails version are active 1.569
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.743
And the expected persistent files created with the old Tails version are present in the filesystem 1.493
And all persistent directories from the old Tails version have safe access rights 2.796
After features/support/hooks.rb:330 1.208
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
7:53.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.484
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.654
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.570
When the network is plugged 0.094
And Tor is ready 50.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.598
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.581
Given I shutdown Tails and wait for the computer to power off 10.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.622
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.658
And the file system changes introduced in version 6.2~testoverlayfs are present 0.401
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.429
# 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.310
When the network is plugged 0.095
And Tor is ready 19.701
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.840
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.522
Given I shutdown Tails and wait for the computer to power off 6.374
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.176
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.554
And the file system changes introduced in version 6.3~testoverlayfs are present 0.583
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.375
When the network is plugged 0.087
And Tor is ready 48.835
Then the Upgrader considers the system as up-to-date 0.343
# 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.361
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.861
After features/support/hooks.rb:330 0.807
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
43.152
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.540
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.551
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 21.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.137
After features/support/hooks.rb:330 1.316
After features/support/hooks.rb:100 0.000