Project Number Date
test_Tails_ISO_stable 5710 11 Jun 2025, 13: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 20:38.913 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:14.894
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 35.436
When I start Tails from USB drive "old" with network unplugged 1:33.730
Then the boot device has safe access rights 3.365
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:330 3.793
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.184
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:28.369
Then Tails is running from USB drive "old" 0.401
And I create a persistent partition 31.768
And I take note of which tps features are available 2.772
Then a Tails persistence partition exists on USB drive "old" 0.909
And I shutdown Tails and wait for the computer to power off 8.756
After features/support/hooks.rb:330 0.238
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.106
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.329
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.183
Then Tails is running from USB drive "old" 0.751
And all tps features are active 2.147
When I write some files expected to persist 2.002
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.364
And all persistence configuration files have safe access rights 0.473
And all persistent directories from the old Tails version have safe access rights 2.864
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 6.480
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.006
After features/support/hooks.rb:330 0.173
After features/support/hooks.rb:100 0.011
Tags: @product
2:40.281
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 without a persistent partition and stopped at Tails Greeter's login screen 12.340
And I log in to a new session 22.321
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.048
And I plug USB drive "to_upgrade" 2.490
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.369
Then the running Tails is installed on USB drive "to_upgrade" 24.197
And I unplug USB drive "to_upgrade" 0.279
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:330 2.239
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.574
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.923
Then all tps features from the old Tails version are active 3.813
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 4.204
And the expected persistent files created with the old Tails version are present in the filesystem 2.087
And all persistent directories from the old Tails version have safe access rights 2.947
After features/support/hooks.rb:330 1.457
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:14.616
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.242
And no SquashFS delta is installed 0.179
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.346
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.549
When the network is plugged 0.085
And Tor is ready 23.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.898
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.263
Given I shutdown Tails and wait for the computer to power off 11.125
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.221
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.477
And the file system changes introduced in version 6.2~testoverlayfs are present 0.405
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.351
# 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 1.174
When the network is plugged 0.081
And Tor is ready 19.700
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.526
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.760
Given I shutdown Tails and wait for the computer to power off 6.817
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.704
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.447
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.079
And Tor is ready 19.959
Then the Upgrader considers the system as up-to-date 0.347
# 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.699
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.631
After features/support/hooks.rb:330 0.852
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
47.255
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 15.505
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.987
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the signing key used by the Upgrader is outdated 0.118
But a current signing key is available on our website 0.000
When the network is plugged 0.122
And Tor is ready 21.191
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.218
After features/support/hooks.rb:330 1.970
After features/support/hooks.rb:100 0.000