Project Number Date
test_Tails_ISO_stable 5504 10 Mar 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 19:4.258 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:3.175
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.286
When I start Tails from USB drive "old" with network unplugged 1:28.554
Then the boot device has safe access rights 3.042
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.080
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.195
After features/support/hooks.rb:330 3.504
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.295
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:26.101
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 32.889
And I take note of which tps features are available 1.559
Then a Tails persistence partition exists on USB drive "old" 0.805
And I shutdown Tails and wait for the computer to power off 8.356
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.010
Tags: @product
2:56.728
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.261
Then Tails is running from USB drive "old" 1.834
And all tps features are active 2.154
When I write some files expected to persist 3.315
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.465
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 6.415
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.916
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.935
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 11.266
And I log in to a new session 19.144
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.611
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.280
Then the running Tails is installed on USB drive "to_upgrade" 21.782
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:330 1.964
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.023
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.453
Then all tps features from the old Tails version are active 1.595
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.294
And the expected persistent files created with the old Tails version are present in the filesystem 1.715
And all persistent directories from the old Tails version have safe access rights 2.413
After features/support/hooks.rb:330 1.108
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:32.745
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 14.914
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.509
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.645
When the network is plugged 0.207
And Tor is ready 23.208
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.719
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.684
Given I shutdown Tails and wait for the computer to power off 11.220
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.823
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.238
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.249
When the network is plugged 0.087
And Tor is ready 17.081
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.836
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.019
Given I shutdown Tails and wait for the computer to power off 4.306
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.663
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.988
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.070
And Tor is ready 17.290
Then the Upgrader considers the system as up-to-date 0.334
# 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.481
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.881
After features/support/hooks.rb:330 0.830
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.355
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 9.800
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 19.824
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.076
After features/support/hooks.rb:330 1.141
After features/support/hooks.rb:100 0.000