Project Number Date
test_Tails_ISO_stable 5690 31 May 2025, 12:54

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:42.152 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:9.386
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 30.464
When I start Tails from USB drive "old" with network unplugged 1:33.393
Then the boot device has safe access rights 3.111
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.400
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.548
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.355
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:28.262
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 30.169
And I take note of which tps features are available 2.195
Then a Tails persistence partition exists on USB drive "old" 0.760
And I shutdown Tails and wait for the computer to power off 8.445
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.008
Tags: @product
3:9.750
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.001
Then Tails is running from USB drive "old" 0.365
And all tps features are active 2.097
When I write some files expected to persist 1.685
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.497
And all persistent directories from the old Tails version have safe access rights 2.517
And I take note of which tps features are available 0.442
And I shutdown Tails and wait for the computer to power off 4.413
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.280
After features/support/hooks.rb:330 0.121
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.933
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 without a persistent partition and stopped at Tails Greeter's login screen 10.082
And I log in to a new session 18.647
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.952
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.819
Then the running Tails is installed on USB drive "to_upgrade" 22.556
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 6.573
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.709
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.802
Then all tps features from the old Tails version are active 1.593
And Tails is running from USB drive "to_upgrade" 0.426
And the boot device has safe access rights 3.612
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.583
After features/support/hooks.rb:330 1.692
After features/support/hooks.rb:100 0.010
7:41.509
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 10.982
And no SquashFS delta is installed 0.217
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.436
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.137
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.091
And Tor is ready 50.849
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.595
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.707
Given I shutdown Tails and wait for the computer to power off 8.895
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.201
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.112
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.303
When the network is plugged 0.068
And Tor is ready 48.787
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.634
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.415
Given I shutdown Tails and wait for the computer to power off 4.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.819
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.087
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.059
And Tor is ready 46.678
Then the Upgrader considers the system as up-to-date 0.310
# 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.390
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.779
After features/support/hooks.rb:330 0.749
After features/support/hooks.rb:100 0.015
40.507
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 10.317
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.503
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.131
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 20.803
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.613
After features/support/hooks.rb:330 0.885
After features/support/hooks.rb:100 0.000