Project Number Date
test_Tails_ISO_stable 5688 30 May 2025, 13:18

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 22:20.061 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:11.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.231
When I start Tails from USB drive "old" with network unplugged 1:33.773
Then the boot device has safe access rights 3.895
And Tails is running from USB drive "old" 0.478
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.350
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:330 3.763
After features/support/hooks.rb:100 0.031
Tags: @product
2:20.662
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:36.750
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 31.607
And I take note of which tps features are available 2.170
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.754
After features/support/hooks.rb:330 0.225
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.220
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.053
Then Tails is running from USB drive "old" 0.379
And all tps features are active 1.943
When I write some files expected to persist 1.949
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 3.120
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 4.384
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.984
After features/support/hooks.rb:330 0.120
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.640
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 13.575
And I log in to a new session 21.397
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.020
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.890
Then the running Tails is installed on USB drive "to_upgrade" 28.791
And I unplug USB drive "to_upgrade" 0.253
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 2.359
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.261
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.761
Then all tps features from the old Tails version are active 1.964
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.669
And the expected persistent files created with the old Tails version are present in the filesystem 1.472
And all persistent directories from the old Tails version have safe access rights 2.433
After features/support/hooks.rb:330 1.282
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
8:55.449
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 14.810
And no SquashFS delta is installed 0.146
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.116
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.069
And Tor is ready 23.564
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.896
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.603
Given I shutdown Tails and wait for the computer to power off 1:24.706
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.122
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.653
And the file system changes introduced in version 6.2~testoverlayfs are present 0.446
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.379
When the network is plugged 0.069
And Tor is ready 20.076
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.228
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.173
Given I shutdown Tails and wait for the computer to power off 6.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.761
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.130
And the file system changes introduced in version 6.3~testoverlayfs are present 0.732
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.338
When the network is plugged 0.094
And Tor is ready 47.644
Then the Upgrader considers the system as up-to-date 0.312
# 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.053
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.635
After features/support/hooks.rb:330 0.759
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
37.736
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 9.938
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 20.276
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.955
After features/support/hooks.rb:330 0.677
After features/support/hooks.rb:100 0.000