Project Number Date
test_Tails_ISO_stable 5698 04 Jun 2025, 13:33

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 19:54.461 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:14.697
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 1.276
And I create a 7200 MiB disk named "old" 0.882
And I plug USB drive "old" 1.151
And I write an old version of the Tails USB image to disk "old" 31.929
When I start Tails from USB drive "old" with network unplugged 1:35.347
Then the boot device has safe access rights 3.101
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:330 3.512
After features/support/hooks.rb:100 0.057
Tags: @product
2:4.762
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:23.728
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 29.798
And I take note of which tps features are available 1.610
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.364
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
3:10.282
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.037
Then Tails is running from USB drive "old" 0.390
And all tps features are active 2.005
When I write some files expected to persist 2.018
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.401
And I take note of which tps features are available 0.409
And I shutdown Tails and wait for the computer to power off 6.674
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.522
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.007
Tags: @product
2:35.743
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 10.668
And I log in to a new session 18.331
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.984
And I plug USB drive "to_upgrade" 2.437
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.329
Then the running Tails is installed on USB drive "to_upgrade" 24.571
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 2.157
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.298
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.528
Then all tps features from the old Tails version are active 1.705
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.510
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.495
After features/support/hooks.rb:330 1.135
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:55.776
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.745
And no SquashFS delta is installed 0.171
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.502
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.078
And Tor is ready 19.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.219
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.096
Given I shutdown Tails and wait for the computer to power off 8.547
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.043
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 4.958
And the file system changes introduced in version 6.2~testoverlayfs are present 0.358
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.331
When the network is plugged 0.077
And Tor is ready 45.594
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.595
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.437
Given I shutdown Tails and wait for the computer to power off 4.448
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.470
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.204
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.081
And Tor is ready 18.844
Then the Upgrader considers the system as up-to-date 0.318
# 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.858
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.552
After features/support/hooks.rb:330 0.728
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
37.901
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 9.798
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.551
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.126
And the signing key used by the Upgrader is outdated 0.193
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 18.884
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.258
After features/support/hooks.rb:330 0.682
After features/support/hooks.rb:100 0.000