Project Number Date
test_Tails_ISO_stable 5658 19 May 2025, 16:19

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:27.243 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:32.660
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.071
And I write an old version of the Tails USB image to disk "old" 33.409
When I start Tails from USB drive "old" with network unplugged 1:53.211
Then the boot device has safe access rights 3.550
And Tails is running from USB drive "old" 0.382
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.403
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 7.529
After features/support/hooks.rb:100 0.007
Tags: @product
2:23.542
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:37.152
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 32.589
And I take note of which tps features are available 2.679
Then a Tails persistence partition exists on USB drive "old" 0.909
And I shutdown Tails and wait for the computer to power off 9.650
After features/support/hooks.rb:330 0.289
After features/support/hooks.rb:100 0.008
Tags: @product
3:18.425
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.542
Then Tails is running from USB drive "old" 0.513
And all tps features are active 3.592
When I write some files expected to persist 2.501
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.865
And I take note of which tps features are available 0.560
And I shutdown Tails and wait for the computer to power off 6.510
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.459
After features/support/hooks.rb:330 0.125
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.907
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 12.337
And I log in to a new session 22.168
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.195
And I plug USB drive "to_upgrade" 2.786
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.732
Then the running Tails is installed on USB drive "to_upgrade" 29.277
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 6.584
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.928
Then all tps features from the old Tails version are active 2.131
And Tails is running from USB drive "to_upgrade" 0.495
And the boot device has safe access rights 3.993
And the expected persistent files created with the old Tails version are present in the filesystem 1.688
And all persistent directories from the old Tails version have safe access rights 2.959
After features/support/hooks.rb:330 0.914
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:13.141
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 12.938
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.544
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.082
And Tor is ready 24.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.932
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.973
Given I shutdown Tails and wait for the computer to power off 9.196
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.230
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.463
And the file system changes introduced in version 6.2~testoverlayfs are present 0.393
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.321
When the network is plugged 0.086
And Tor is ready 20.037
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.023
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.661
Given I shutdown Tails and wait for the computer to power off 6.764
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.612
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.412
And the file system changes introduced in version 6.3~testoverlayfs are present 0.554
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.374
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.432
When the network is plugged 0.113
And Tor is ready 20.346
Then the Upgrader considers the system as up-to-date 0.330
# 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 16.758
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.427
After features/support/hooks.rb:330 0.762
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.188
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 11.467
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.133
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 19.124
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.985
After features/support/hooks.rb:330 1.561
After features/support/hooks.rb:100 0.000