Project Number Date
test_Tails_ISO_stable 5668 21 May 2025, 21:10

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 19:45.684 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:6.839
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 1.004
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.854
When I start Tails from USB drive "old" with network unplugged 1:29.741
Then the boot device has safe access rights 3.123
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 7.369
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.779
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.286
And I start Tails from USB drive "old" with network unplugged and I login 1:30.051
Then Tails is running from USB drive "old" 0.401
And I create a persistent partition 29.872
And I take note of which tps features are available 2.170
Then a Tails persistence partition exists on USB drive "old" 0.804
And I shutdown Tails and wait for the computer to power off 8.192
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.009
Tags: @product
3:9.852
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.194
Then Tails is running from USB drive "old" 0.375
And all tps features are active 2.048
When I write some files expected to persist 2.091
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 3.169
And I take note of which tps features are available 0.407
And I shutdown Tails and wait for the computer to power off 4.379
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.293
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.300
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 9.864
And I log in to a new session 19.140
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.037
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.094
Then the running Tails is installed on USB drive "to_upgrade" 28.276
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 2.082
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.471
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.257
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.497
Then all tps features from the old Tails version are active 1.493
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.111
And the expected persistent files created with the old Tails version are present in the filesystem 1.274
And all persistent directories from the old Tails version have safe access rights 2.513
After features/support/hooks.rb:330 1.434
After features/support/hooks.rb:100 0.009
6:42.074
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 13.092
And no SquashFS delta is installed 0.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.465
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.398
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.498
When the network is plugged 0.067
And Tor is ready 24.017
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.056
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.043
Given I shutdown Tails and wait for the computer to power off 8.561
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.136
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.056
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.315
When the network is plugged 0.077
And Tor is ready 19.046
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.723
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.356
Given I shutdown Tails and wait for the computer to power off 4.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.432
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 1.900
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.382
When the network is plugged 0.062
And Tor is ready 19.106
Then the Upgrader considers the system as up-to-date 0.319
# 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.852
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.879
After features/support/hooks.rb:330 0.692
After features/support/hooks.rb:100 0.016
41.366
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.033
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.103
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 21.064
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.968
After features/support/hooks.rb:330 1.573
After features/support/hooks.rb:100 0.000