Project Number Date
test_Tails_ISO_stable 5706 10 Jun 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 20:8.381 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.394
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.259
When I start Tails from USB drive "old" with network unplugged 1:30.588
Then the boot device has safe access rights 3.144
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:330 6.831
After features/support/hooks.rb:100 0.012
Tags: @product
2:9.287
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:26.048
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 31.577
And I take note of which tps features are available 2.103
Then a Tails persistence partition exists on USB drive "old" 0.820
And I shutdown Tails and wait for the computer to power off 8.217
After features/support/hooks.rb:330 0.173
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.127
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.145
Then Tails is running from USB drive "old" 1.130
And all tps features are active 2.212
When I write some files expected to persist 2.123
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 1.055
And all persistent directories from the old Tails version have safe access rights 3.844
And I take note of which tps features are available 0.438
And I shutdown Tails and wait for the computer to power off 4.458
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.294
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.168
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 10.178
And I log in to a new session 19.148
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.818
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.195
Then the running Tails is installed on USB drive "to_upgrade" 25.749
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.432
After features/support/hooks.rb:330 6.675
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.044
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.926
Then all tps features from the old Tails version are active 1.710
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.608
And the expected persistent files created with the old Tails version are present in the filesystem 1.562
And all persistent directories from the old Tails version have safe access rights 2.685
After features/support/hooks.rb:330 1.533
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:20.512
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 12.044
And no SquashFS delta is installed 0.226
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.443
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.463
When the network is plugged 0.067
And Tor is ready 22.800
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.079
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.137
Given I shutdown Tails and wait for the computer to power off 11.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.584
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.119
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.282
When the network is plugged 0.075
And Tor is ready 48.158
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.589
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.462
Given I shutdown Tails and wait for the computer to power off 6.528
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.019
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.129
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.068
And Tor is ready 18.095
Then the Upgrader considers the system as up-to-date 10.746
# 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.217
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.485
After features/support/hooks.rb:330 0.779
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
37.846
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 10.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.416
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the signing key used by the Upgrader is outdated 0.127
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 18.172
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.839
After features/support/hooks.rb:330 1.086
After features/support/hooks.rb:100 0.000