Project Number Date
test_Tails_ISO_stable 5620 01 May 2025, 13:20

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 24:12.413 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:44.584
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.354
And I create a 7200 MiB disk named "old" 0.266
And I plug USB drive "old" 1.206
And I write an old version of the Tails USB image to disk "old" 46.939
When I start Tails from USB drive "old" with network unplugged 1:50.966
Then the boot device has safe access rights 3.552
And Tails is running from USB drive "old" 0.471
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.360
And I unplug USB drive "old" 0.278
After features/support/hooks.rb:330 4.200
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.726
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.802
And I start Tails from USB drive "old" with network unplugged and I login 1:41.807
Then Tails is running from USB drive "old" 0.449
And I create a persistent partition 41.949
And I take note of which tps features are available 15.220
Then a Tails persistence partition exists on USB drive "old" 1.615
And I shutdown Tails and wait for the computer to power off 10.882
After features/support/hooks.rb:330 0.269
After features/support/hooks.rb:100 0.012
Tags: @product
4:3.599
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 1.621
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:9.937
Then Tails is running from USB drive "old" 0.539
And all tps features are active 4.527
When I write some files expected to persist 2.463
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.309
And all persistence configuration files have safe access rights 0.523
And all persistent directories from the old Tails version have safe access rights 3.574
And I take note of which tps features are available 2.557
And I shutdown Tails and wait for the computer to power off 9.147
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.396
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.011
Tags: @product
3:3.940
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 24.017
And I log in to a new session 22.541
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.388
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.730
Then the running Tails is installed on USB drive "to_upgrade" 29.201
And I unplug USB drive "to_upgrade" 0.317
And I unplug USB drive "__internal" 0.274
After features/support/hooks.rb:330 3.320
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.306
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.531
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.234
Then all tps features from the old Tails version are active 2.198
And Tails is running from USB drive "to_upgrade" 0.396
And the boot device has safe access rights 4.074
And the expected persistent files created with the old Tails version are present in the filesystem 1.848
And all persistent directories from the old Tails version have safe access rights 3.022
After features/support/hooks.rb:330 1.531
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
8:5.958
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 26.739
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.614
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.553
When the network is plugged 0.105
And Tor is ready 25.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.469
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.874
Given I shutdown Tails and wait for the computer to power off 8.898
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.298
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.606
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.404
# 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.429
When the network is plugged 0.141
And Tor is ready 22.279
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.333
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.526
Given I shutdown Tails and wait for the computer to power off 7.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.690
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 6.828
And the file system changes introduced in version 6.3~testoverlayfs are present 0.637
And only the 6.3~testoverlayfs SquashFS delta is installed 0.119
# 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.386
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.485
When the network is plugged 0.740
And Tor is ready 21.073
Then the Upgrader considers the system as up-to-date 0.509
# 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 22.187
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.068
After features/support/hooks.rb:330 0.872
After features/support/hooks.rb:100 0.051
Tags: @product @automatic_upgrade
48.296
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.869
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.482
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.164
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 24.576
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.019
After features/support/hooks.rb:330 0.812
After features/support/hooks.rb:100 0.000