Project Number Date
test_Tails_ISO_stable 5672 23 May 2025, 12: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 18:45.447 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:0.535
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.378
And I create a 7200 MiB disk named "old" 0.108
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.836
When I start Tails from USB drive "old" with network unplugged 1:24.134
Then the boot device has safe access rights 3.042
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:330 3.519
After features/support/hooks.rb:100 0.011
Tags: @product
2:8.071
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:26.777
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 31.860
And I take note of which tps features are available 1.563
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 6.540
After features/support/hooks.rb:330 0.168
After features/support/hooks.rb:100 0.007
Tags: @product
2:49.744
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.589
Then Tails is running from USB drive "old" 1.261
And all tps features are active 2.123
When I write some files expected to persist 2.488
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.475
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.460
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.142
After features/support/hooks.rb:330 0.126
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.402
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 without a persistent partition and stopped at Tails Greeter's login screen 10.087
And I log in to a new session 20.042
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.983
And I plug USB drive "to_upgrade" 2.364
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.906
Then the running Tails is installed on USB drive "to_upgrade" 29.577
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 1.116
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.064
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.497
Then all tps features from the old Tails version are active 1.771
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.240
And the expected persistent files created with the old Tails version are present in the filesystem 1.419
And all persistent directories from the old Tails version have safe access rights 2.560
After features/support/hooks.rb:330 1.484
After features/support/hooks.rb:100 0.009
6:23.807
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 14.133
And no SquashFS delta is installed 0.228
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.386
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.359
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.509
When the network is plugged 0.076
And Tor is ready 20.148
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.963
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.879
Given I shutdown Tails and wait for the computer to power off 10.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.645
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.026
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.283
# 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.270
When the network is plugged 0.077
And Tor is ready 18.766
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.569
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.849
Given I shutdown Tails and wait for the computer to power off 4.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.560
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.952
And the file system changes introduced in version 6.3~testoverlayfs are present 0.528
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.281
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.072
And Tor is ready 17.713
Then the Upgrader considers the system as up-to-date 0.290
# 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 14.787
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.575
After features/support/hooks.rb:330 0.716
After features/support/hooks.rb:100 0.020
37.821
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 11.361
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.461
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.120
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 18.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.743
After features/support/hooks.rb:330 0.754
After features/support/hooks.rb:100 0.000