Project Number Date
test_Tails_ISO_devel 3899 07 Jul 2025, 14:42

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 28:16.138 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
3:8.126
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.033
Given a computer 1.525
And I create a 7200 MiB disk named "old" 0.209
And I plug USB drive "old" 1.140
And I write an old version of the Tails USB image to disk "old" 42.044
When I start Tails from USB drive "old" with network unplugged 2:18.623
Then the boot device has safe access rights 3.513
And Tails is running from USB drive "old" 0.395
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:330 3.704
After features/support/hooks.rb:100 0.017
Tags: @product
3:8.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.276
And I start Tails from USB drive "old" with network unplugged and I login 1:59.121
Then Tails is running from USB drive "old" 0.625
And I create a persistent partition 50.940
And I take note of which tps features are available 2.735
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 13.642
After features/support/hooks.rb:330 0.356
After features/support/hooks.rb:100 0.040
Tags: @product
4:8.754
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.031
Given a computer 0.641
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:9.693
Then Tails is running from USB drive "old" 0.527
And all tps features are active 3.399
When I write some files expected to persist 8.208
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.485
And all persistence configuration files have safe access rights 0.585
And all persistent directories from the old Tails version have safe access rights 2.941
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 6.835
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 34.958
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.009
Tags: @product
3:28.774
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 17.761
And I log in to a new session 25.316
And I clone USB drive "old" to a new USB drive "to_upgrade" 5.042
And I plug USB drive "to_upgrade" 3.919
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.972
Then the running Tails is installed on USB drive "to_upgrade" 41.645
And I unplug USB drive "to_upgrade" 1.914
And I unplug USB drive "__internal" 3.202
After features/support/hooks.rb:330 1.844
After features/support/hooks.rb:100 0.000
Tags: @product
3:5.361
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given a computer 0.410
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:47.507
Then all tps features from the old Tails version are active 2.010
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 7.847
And the expected persistent files created with the old Tails version are present in the filesystem 4.058
And all persistent directories from the old Tails version have safe access rights 3.174
After features/support/hooks.rb:330 1.552
After features/support/hooks.rb:100 0.010
10:25.129
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 13.326
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.828
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.548
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.711
When the network is plugged 0.234
And Tor is ready 28.207
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.341
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.019
Given I shutdown Tails and wait for the computer to power off 1:44.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:39.286
Then Tails is running version 6.2~testoverlayfs 0.039
And all tps features are active 2.485
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
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.369
# 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.449
When the network is plugged 0.070
And Tor is ready 30.611
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.370
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.668
Given I shutdown Tails and wait for the computer to power off 6.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:53.890
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.319
And the file system changes introduced in version 6.3~testoverlayfs are present 0.529
And only the 6.3~testoverlayfs SquashFS delta is installed 0.109
# 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.363
When the network is plugged 0.084
And Tor is ready 22.570
Then the Upgrader considers the system as up-to-date 0.397
# 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 20.497
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.941
After features/support/hooks.rb:330 1.547
After features/support/hooks.rb:100 0.488
51.848
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.235
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.693
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.664
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.124
And Tor is ready 28.256
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.967
After features/support/hooks.rb:330 0.925
After features/support/hooks.rb:100 0.000