Project Number Date
test_Tails_ISO_stable 5695 03 Jun 2025, 13: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 20:40.316 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:29.065
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 33.927
When I start Tails from USB drive "old" with network unplugged 1:49.138
Then the boot device has safe access rights 3.582
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.370
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:330 3.766
After features/support/hooks.rb:100 0.027
Tags: @product
2:31.830
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.281
And I start Tails from USB drive "old" with network unplugged and I login 1:45.939
Then Tails is running from USB drive "old" 0.416
And I create a persistent partition 32.303
And I take note of which tps features are available 2.674
Then a Tails persistence partition exists on USB drive "old" 0.990
And I shutdown Tails and wait for the computer to power off 9.223
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.866
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.698
Then Tails is running from USB drive "old" 0.457
And all tps features are active 2.213
When I write some files expected to persist 2.366
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 2.570
And I take note of which tps features are available 0.450
And I shutdown Tails and wait for the computer to power off 4.455
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.730
After features/support/hooks.rb:330 0.133
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.837
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 10.669
And I log in to a new session 21.002
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.598
And I plug USB drive "to_upgrade" 2.449
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.127
Then the running Tails is installed on USB drive "to_upgrade" 23.431
And I unplug USB drive "to_upgrade" 0.297
And I unplug USB drive "__internal" 0.261
After features/support/hooks.rb:330 3.886
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.419
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.689
Then all tps features from the old Tails version are active 1.772
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 4.005
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.835
After features/support/hooks.rb:330 1.516
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:54.680
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 12.804
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.470
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.152
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.520
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.067
And Tor is ready 21.771
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.614
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.255
Given I shutdown Tails and wait for the computer to power off 8.704
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.505
Then Tails is running version 6.2~testoverlayfs 0.040
And all tps features are active 2.498
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.386
When the network is plugged 0.086
And Tor is ready 19.905
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.680
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.285
Given I shutdown Tails and wait for the computer to power off 6.557
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.824
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.452
And the file system changes introduced in version 6.3~testoverlayfs are present 0.540
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.064
And Tor is ready 20.527
Then the Upgrader considers the system as up-to-date 0.335
# 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 15.428
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.243
After features/support/hooks.rb:330 0.714
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
40.617
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.413
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.145
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 20.243
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.312
After features/support/hooks.rb:330 0.857
After features/support/hooks.rb:100 0.000