Project Number Date
test_Tails_ISO_stable 5489 04 Mar 2025, 08: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:9.519 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:26.384
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.143
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 38.277
When I start Tails from USB drive "old" with network unplugged 1:42.573
Then the boot device has safe access rights 3.104
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 3.565
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.980
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:29.020
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 33.212
And I take note of which tps features are available 1.813
Then a Tails persistence partition exists on USB drive "old" 0.868
And I shutdown Tails and wait for the computer to power off 8.515
After features/support/hooks.rb:330 0.238
After features/support/hooks.rb:100 0.010
Tags: @product
3:3.261
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.020
Then Tails is running from USB drive "old" 0.371
And all tps features are active 2.000
When I write some files expected to persist 1.960
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.508
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 4.540
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.547
After features/support/hooks.rb:330 0.142
After features/support/hooks.rb:100 0.011
Tags: @product
2:28.607
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 11.777
And I log in to a new session 19.348
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.823
And I plug USB drive "to_upgrade" 2.437
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.982
Then the running Tails is installed on USB drive "to_upgrade" 18.818
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:330 2.879
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.117
Then all tps features from the old Tails version are active 2.142
And Tails is running from USB drive "to_upgrade" 0.595
And the boot device has safe access rights 3.961
And the expected persistent files created with the old Tails version are present in the filesystem 1.746
And all persistent directories from the old Tails version have safe access rights 2.589
After features/support/hooks.rb:330 1.233
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:57.568
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 12.749
And no SquashFS delta is installed 0.540
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.635
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.555
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.612
When the network is plugged 0.077
And Tor is ready 21.401
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.293
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.535
Given I shutdown Tails and wait for the computer to power off 8.972
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.793
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.560
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.311
When the network is plugged 0.072
And Tor is ready 21.100
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.148
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.224
Given I shutdown Tails and wait for the computer to power off 4.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.160
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.425
And the file system changes introduced in version 6.3~testoverlayfs are present 0.523
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.303
When the network is plugged 0.105
And Tor is ready 19.615
Then the Upgrader considers the system as up-to-date 0.311
# 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.884
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.012
After features/support/hooks.rb:330 0.752
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.338
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.541
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the signing key used by the Upgrader is outdated 0.416
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 20.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.087
After features/support/hooks.rb:330 0.733
After features/support/hooks.rb:100 0.000