Project Number Date
test_Tails_ISO_devel 3843 29 May 2025, 13:21

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 23:40.176 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:50.119
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 36.887
When I start Tails from USB drive "old" with network unplugged 2:6.547
Then the boot device has safe access rights 4.158
And Tails is running from USB drive "old" 0.402
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.268
After features/support/hooks.rb:330 7.936
After features/support/hooks.rb:100 0.017
Tags: @product
2:44.871
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.357
And I start Tails from USB drive "old" with network unplugged and I login 1:53.571
Then Tails is running from USB drive "old" 0.407
And I create a persistent partition 36.728
And I take note of which tps features are available 2.741
Then a Tails persistence partition exists on USB drive "old" 1.001
And I shutdown Tails and wait for the computer to power off 10.063
After features/support/hooks.rb:330 0.184
After features/support/hooks.rb:100 0.011
Tags: @product
3:29.005
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 2.420
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:42.435
Then Tails is running from USB drive "old" 0.422
And all tps features are active 2.653
When I write some files expected to persist 2.080
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.583
And all persistent directories from the old Tails version have safe access rights 3.376
And I take note of which tps features are available 0.639
And I shutdown Tails and wait for the computer to power off 6.801
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.322
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.013
Tags: @product
3:22.992
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 36.636
And I log in to a new session 20.980
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.975
And I plug USB drive "to_upgrade" 2.607
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:56.884
Then the running Tails is installed on USB drive "to_upgrade" 23.434
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:330 3.143
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.270
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.024
Then all tps features from the old Tails version are active 2.250
And Tails is running from USB drive "to_upgrade" 0.427
And the boot device has safe access rights 3.975
And the expected persistent files created with the old Tails version are present in the filesystem 1.839
And all persistent directories from the old Tails version have safe access rights 2.925
After features/support/hooks.rb:330 1.682
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:57.331
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 17.147
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.358
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.477
When the network is plugged 0.650
And Tor is ready 51.165
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.472
Given I shutdown Tails and wait for the computer to power off 10.989
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:46.764
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 6.921
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.364
When the network is plugged 0.384
And Tor is ready 20.981
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.185
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.817
Given I shutdown Tails and wait for the computer to power off 4.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.303
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.297
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.377
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.386
When the network is plugged 0.112
And Tor is ready 18.044
Then the Upgrader considers the system as up-to-date 0.297
# 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.451
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.158
After features/support/hooks.rb:330 0.732
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
42.141
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 14.029
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.138
But a current signing key is available on our website 0.000
When the network is plugged 0.115
And Tor is ready 20.343
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.085
After features/support/hooks.rb:330 0.954
After features/support/hooks.rb:100 0.000