Project Number Date
test_Tails_ISO_devel 3839 27 May 2025, 15: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 20:26.473 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:21.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 34.379
When I start Tails from USB drive "old" with network unplugged 1:40.939
Then the boot device has safe access rights 3.446
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 3.556
After features/support/hooks.rb:100 0.040
Tags: @product
2:19.669
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login 1:33.924
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 33.154
And I take note of which tps features are available 1.879
Then a Tails persistence partition exists on USB drive "old" 0.968
And I shutdown Tails and wait for the computer to power off 9.115
After features/support/hooks.rb:330 0.221
After features/support/hooks.rb:100 0.031
Tags: @product
3:10.952
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.030
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.731
Then Tails is running from USB drive "old" 0.409
And all tps features are active 3.058
When I write some files expected to persist 1.750
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.307
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 4.537
And I take note of which tps features are available 1.685
And I shutdown Tails and wait for the computer to power off 6.359
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.470
After features/support/hooks.rb:330 0.114
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.269
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 without a persistent partition and stopped at Tails Greeter's login screen 12.213
And I log in to a new session 19.730
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.721
And I plug USB drive "to_upgrade" 2.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.306
Then the running Tails is installed on USB drive "to_upgrade" 24.295
And I unplug USB drive "to_upgrade" 0.311
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:330 2.161
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.577
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.327
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.407
Then all tps features from the old Tails version are active 1.788
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.818
And the expected persistent files created with the old Tails version are present in the filesystem 1.424
And all persistent directories from the old Tails version have safe access rights 2.493
After features/support/hooks.rb:330 1.182
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:45.770
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.542
And no SquashFS delta is installed 0.148
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.349
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.521
And Tor is ready 21.894
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.401
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.831
Given I shutdown Tails and wait for the computer to power off 9.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.041
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.431
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.268
When the network is plugged 0.078
And Tor is ready 18.773
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.105
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.848
Given I shutdown Tails and wait for the computer to power off 6.978
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.629
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.094
And the file system changes introduced in version 6.3~testoverlayfs are present 0.575
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.066
And Tor is ready 20.684
Then the Upgrader considers the system as up-to-date 0.373
# 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.238
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.498
After features/support/hooks.rb:330 0.725
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
45.083
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.585
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.146
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 25.439
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.371
After features/support/hooks.rb:330 1.186
After features/support/hooks.rb:100 0.000