Project Number Date
test_Tails_ISO_feature-arti 110 08 Jul 2025, 01:13

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 23:39.413 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:42.767
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 39.108
When I start Tails from USB drive "old" with network unplugged 1:57.917
Then the boot device has safe access rights 3.441
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 0.861
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.117
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:40.404
Then Tails is running from USB drive "old" 0.531
And I create a persistent partition 36.813
And I take note of which tps features are available 2.050
Then a Tails persistence partition exists on USB drive "old" 1.104
And I shutdown Tails and wait for the computer to power off 9.037
After features/support/hooks.rb:330 0.197
After features/support/hooks.rb:100 0.008
Tags: @product
3:28.327
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:42.668
Then Tails is running from USB drive "old" 2.362
And all tps features are active 1.894
When I write some files expected to persist 1.934
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.477
And all persistent directories from the old Tails version have safe access rights 2.924
And I take note of which tps features are available 0.528
And I shutdown Tails and wait for the computer to power off 6.330
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.769
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.007
Tags: @product
2:59.476
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 13.135
And I log in to a new session 24.011
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.893
And I plug USB drive "to_upgrade" 2.485
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.246
Then the running Tails is installed on USB drive "to_upgrade" 34.245
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:330 3.610
After features/support/hooks.rb:100 0.000
Tags: @product
2:42.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.260
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:31.937
Then all tps features from the old Tails version are active 2.177
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.332
And the expected persistent files created with the old Tails version are present in the filesystem 1.638
And all persistent directories from the old Tails version have safe access rights 2.898
After features/support/hooks.rb:330 1.825
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
8:12.294
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.067
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.805
And no SquashFS delta is installed 0.337
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.623
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.133
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.409
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.075
And Tor is ready 23.420
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.058
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.185
Given I shutdown Tails and wait for the computer to power off 11.577
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:30.953
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 3.218
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.299
When the network is plugged 0.065
And Tor is ready 52.060
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.651
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.146
Given I shutdown Tails and wait for the computer to power off 7.214
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.449
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.480
And the file system changes introduced in version 6.3~testoverlayfs are present 0.660
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.471
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.456
When the network is plugged 0.161
And Tor is ready 22.469
Then the Upgrader considers the system as up-to-date 0.292
# 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 19.732
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.469
After features/support/hooks.rb:330 0.761
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
1:3.833
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 13.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.768
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.099
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 48.960
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.818
After features/support/hooks.rb:330 1.359
After features/support/hooks.rb:100 0.000