Project Number Date
test_Tails_ISO_stable 5752 01 Jul 2025, 09:38

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 21:36.736 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:27.952
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.098
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 31.678
When I start Tails from USB drive "old" with network unplugged 1:50.954
Then the boot device has safe access rights 2.901
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:330 7.951
After features/support/hooks.rb:100 0.022
Tags: @product
2:21.906
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.293
And I start Tails from USB drive "old" with network unplugged and I login 1:34.767
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 34.790
And I take note of which tps features are available 2.384
Then a Tails persistence partition exists on USB drive "old" 0.835
And I shutdown Tails and wait for the computer to power off 8.499
After features/support/hooks.rb:330 0.216
After features/support/hooks.rb:100 0.051
Tags: @product
3:28.346
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.277
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:45.587
Then Tails is running from USB drive "old" 0.370
And all tps features are active 2.126
When I write some files expected to persist 1.973
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.290
And all persistence configuration files have safe access rights 0.532
And all persistent directories from the old Tails version have safe access rights 2.847
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 7.504
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.391
After features/support/hooks.rb:330 0.110
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.165
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.429
And I log in to a new session 21.006
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.972
And I plug USB drive "to_upgrade" 2.661
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.630
Then the running Tails is installed on USB drive "to_upgrade" 24.012
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 0.908
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.491
Then all tps features from the old Tails version are active 3.471
And Tails is running from USB drive "to_upgrade" 0.522
And the boot device has safe access rights 3.712
And the expected persistent files created with the old Tails version are present in the filesystem 1.648
And all persistent directories from the old Tails version have safe access rights 2.701
After features/support/hooks.rb:330 0.985
After features/support/hooks.rb:100 0.009
7:18.968
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 11.773
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.666
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.387
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.125
And Tor is ready 23.175
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.994
Given I shutdown Tails and wait for the computer to power off 8.832
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.091
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.389
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.560
# 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.802
When the network is plugged 0.656
And Tor is ready 21.100
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.467
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.738
Given I shutdown Tails and wait for the computer to power off 7.061
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.917
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.890
And the file system changes introduced in version 6.3~testoverlayfs are present 0.646
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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.364
When the network is plugged 0.066
And Tor is ready 20.024
Then the Upgrader considers the system as up-to-date 0.314
# 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 17.872
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.960
After features/support/hooks.rb:330 0.745
After features/support/hooks.rb:100 0.024
41.632
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.883
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.520
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.121
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 21.769
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.184
After features/support/hooks.rb:330 1.772
After features/support/hooks.rb:100 0.000