Project Number Date
test_Tails_ISO_stable 5719 17 Jun 2025, 17:38

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.947 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:42.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.246
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" 48.422
When I start Tails from USB drive "old" with network unplugged 1:48.367
Then the boot device has safe access rights 3.478
And Tails is running from USB drive "old" 0.476
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.360
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 9.667
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.533
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:47.764
Then Tails is running from USB drive "old" 0.396
And I create a persistent partition 38.607
And I take note of which tps features are available 2.814
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 10.953
After features/support/hooks.rb:330 0.193
After features/support/hooks.rb:100 0.009
Tags: @product
3:42.397
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:53.311
Then Tails is running from USB drive "old" 1.461
And all tps features are active 2.242
When I write some files expected to persist 2.535
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.347
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 2.503
And I take note of which tps features are available 0.404
And I shutdown Tails and wait for the computer to power off 6.985
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.932
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.459
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 14.163
And I log in to a new session 24.164
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.308
And I plug USB drive "to_upgrade" 2.521
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.791
Then the running Tails is installed on USB drive "to_upgrade" 29.100
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 0.756
After features/support/hooks.rb:100 0.000
Tags: @product
2:46.993
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:35.166
Then all tps features from the old Tails version are active 2.884
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.361
And the expected persistent files created with the old Tails version are present in the filesystem 2.154
And all persistent directories from the old Tails version have safe access rights 2.880
After features/support/hooks.rb:330 3.553
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
8:4.103
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.795
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.509
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.391
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.394
When the network is plugged 0.136
And Tor is ready 25.184
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.471
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.727
Given I shutdown Tails and wait for the computer to power off 11.229
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.980
Then Tails is running version 6.2~testoverlayfs 0.231
And all tps features are active 3.164
And the file system changes introduced in version 6.2~testoverlayfs are present 0.422
And only the 6.2~testoverlayfs SquashFS delta is installed 0.135
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.418
When the network is plugged 0.201
And Tor is ready 46.655
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.594
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.012
Given I shutdown Tails and wait for the computer to power off 7.109
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.755
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.247
And the file system changes introduced in version 6.3~testoverlayfs are present 0.504
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.143
And Tor is ready 17.186
Then the Upgrader considers the system as up-to-date 10.880
# 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 18.843
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.525
After features/support/hooks.rb:330 1.158
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
43.599
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 with a persistent partition enabled and logged in 12.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.866
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.195
And the signing key used by the Upgrader is outdated 0.151
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 21.254
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.860
After features/support/hooks.rb:330 1.268
After features/support/hooks.rb:100 0.000