Project Number Date
test_Tails_ISO_stable 5689 31 May 2025, 09:29

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:8.820 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:8.213
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 30.387
When I start Tails from USB drive "old" with network unplugged 1:32.522
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 7.115
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.981
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:26.626
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 32.194
And I take note of which tps features are available 2.492
Then a Tails persistence partition exists on USB drive "old" 0.774
And I shutdown Tails and wait for the computer to power off 8.336
After features/support/hooks.rb:330 0.185
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.650
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.671
Then Tails is running from USB drive "old" 0.315
And all tps features are active 2.047
When I write some files expected to persist 2.100
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.335
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 4.186
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.615
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.007
Tags: @product
2:42.864
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 12.306
And I log in to a new session 19.256
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.735
And I plug USB drive "to_upgrade" 2.603
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.145
Then the running Tails is installed on USB drive "to_upgrade" 27.392
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:330 2.633
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.744
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.049
Then all tps features from the old Tails version are active 1.795
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.317
And the expected persistent files created with the old Tails version are present in the filesystem 1.344
And all persistent directories from the old Tails version have safe access rights 2.681
After features/support/hooks.rb:330 1.301
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:1.571
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 12.284
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.082
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.076
And Tor is ready 25.156
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.902
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.012
Given I shutdown Tails and wait for the computer to power off 11.187
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.379
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.388
And the file system changes introduced in version 6.2~testoverlayfs are present 0.356
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.274
When the network is plugged 0.064
And Tor is ready 46.224
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.598
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.263
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.920
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.053
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.399
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.117
And Tor is ready 19.600
Then the Upgrader considers the system as up-to-date 0.327
# 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 15.768
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.576
After features/support/hooks.rb:330 0.703
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
37.794
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.524
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.105
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 18.212
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.467
After features/support/hooks.rb:330 0.707
After features/support/hooks.rb:100 0.000