Project Number Date
test_Tails_ISO_feature-arti 97 24 Jun 2025, 21: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 36:39.212 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
3:44.554
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given a computer 0.543
And I create a 7200 MiB disk named "old" 0.091
And I plug USB drive "old" 1.092
And I write an old version of the Tails USB image to disk "old" 1:1.710
When I start Tails from USB drive "old" with network unplugged 2:25.667
Then the boot device has safe access rights 14.084
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.381
And I unplug USB drive "old" 0.426
After features/support/hooks.rb:330 4.969
After features/support/hooks.rb:100 0.168
Tags: @product
4:7.180
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.208
Given a computer 3.370
And I start Tails from USB drive "old" with network unplugged and I login 2:32.665
Then Tails is running from USB drive "old" 1.538
And I create a persistent partition 1:2.580
And I take note of which tps features are available 7.745
Then a Tails persistence partition exists on USB drive "old" 3.585
And I shutdown Tails and wait for the computer to power off 15.694
After features/support/hooks.rb:330 0.973
After features/support/hooks.rb:100 0.042
Tags: @product
5:46.317
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.035
Given a computer 1.495
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:22.408
Then Tails is running from USB drive "old" 0.665
And all tps features are active 2.428
When I write some files expected to persist 2.609
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.513
And all persistent directories from the old Tails version have safe access rights 13.420
And I take note of which tps features are available 0.490
And I shutdown Tails and wait for the computer to power off 13.132
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 48.889
After features/support/hooks.rb:330 0.335
After features/support/hooks.rb:100 0.037
Tags: @product
4:22.463
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.796
And I log in to a new session 39.132
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.261
And I plug USB drive "to_upgrade" 11.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:16.906
Then the running Tails is installed on USB drive "to_upgrade" 47.248
And I unplug USB drive "to_upgrade" 0.370
And I unplug USB drive "__internal" 0.335
After features/support/hooks.rb:330 6.935
After features/support/hooks.rb:100 0.000
Tags: @product
4:22.878
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.184
Given a computer 1.493
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:49.580
Then all tps features from the old Tails version are active 2.822
And Tails is running from USB drive "to_upgrade" 2.428
And the boot device has safe access rights 12.614
And the expected persistent files created with the old Tails version are present in the filesystem 3.303
And all persistent directories from the old Tails version have safe access rights 10.635
After features/support/hooks.rb:330 2.283
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
13:10.643
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:12.983
And no SquashFS delta is installed 0.835
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.607
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.714
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.604
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.701
When the network is plugged 0.138
And Tor is ready 41.294
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 17.864
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 23.819
Given I shutdown Tails and wait for the computer to power off 17.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:41.193
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.944
And the file system changes introduced in version 6.2~testoverlayfs are present 0.676
And only the 6.2~testoverlayfs SquashFS delta is installed 0.175
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.429
# 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.536
When the network is plugged 0.072
And Tor is ready 35.533
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 17.868
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 22.663
Given I shutdown Tails and wait for the computer to power off 14.493
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:30.644
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 12.945
And the file system changes introduced in version 6.3~testoverlayfs are present 0.685
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.390
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.066
And Tor is ready 38.682
Then the Upgrader considers the system as up-to-date 0.312
# 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 24.903
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 4.149
After features/support/hooks.rb:330 4.943
After features/support/hooks.rb:100 0.069
Tags: @product @automatic_upgrade
1:5.175
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.164
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 1.305
And the signing key used by the Upgrader is outdated 1.618
But a current signing key is available on our website 0.000
When the network is plugged 0.410
And Tor is ready 31.599
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.763
After features/support/hooks.rb:330 1.678
After features/support/hooks.rb:100 0.000