Project Number Date
test_Tails_ISO_test-suite-options 18 04 Jul 2025, 21:06

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 29:40.565 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:0.994
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 42.669
When I start Tails from USB drive "old" with network unplugged 2:11.707
Then the boot device has safe access rights 4.225
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 3.814
After features/support/hooks.rb:100 0.011
Tags: @product
3:6.200
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 2:3.976
Then Tails is running from USB drive "old" 1.529
And I create a persistent partition 44.655
And I take note of which tps features are available 2.606
Then a Tails persistence partition exists on USB drive "old" 0.823
And I shutdown Tails and wait for the computer to power off 12.368
After features/support/hooks.rb:330 0.579
After features/support/hooks.rb:100 0.050
Tags: @product
4:14.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.985
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:11.630
Then Tails is running from USB drive "old" 0.970
And all tps features are active 5.408
When I write some files expected to persist 3.991
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.504
And all persistence configuration files have safe access rights 0.608
And all persistent directories from the old Tails version have safe access rights 3.053
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 6.779
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 39.658
After features/support/hooks.rb:330 0.181
After features/support/hooks.rb:100 0.009
Tags: @product
3:23.457
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 17.341
And I log in to a new session 34.094
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.307
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.976
Then the running Tails is installed on USB drive "to_upgrade" 33.216
And I unplug USB drive "to_upgrade" 0.281
And I unplug USB drive "__internal" 2.820
After features/support/hooks.rb:330 3.479
After features/support/hooks.rb:100 0.000
Tags: @product
3:12.324
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.542
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:0.017
Then all tps features from the old Tails version are active 3.032
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 3.580
And the expected persistent files created with the old Tails version are present in the filesystem 1.612
And all persistent directories from the old Tails version have safe access rights 3.148
After features/support/hooks.rb:330 4.959
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
11:48.951
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.456
And no SquashFS delta is installed 0.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.119
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.535
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.745
When the network is plugged 0.093
And Tor is ready 59.647
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.872
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.945
Given I shutdown Tails and wait for the computer to power off 11.989
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:57.360
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.791
And the file system changes introduced in version 6.2~testoverlayfs are present 1.676
And only the 6.2~testoverlayfs SquashFS delta is installed 1.363
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.950
# 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 1.156
When the network is plugged 0.244
And Tor is ready 26.563
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.157
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 18.286
Given I shutdown Tails and wait for the computer to power off 1:26.595
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:54.025
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.818
And the file system changes introduced in version 6.3~testoverlayfs are present 6.192
And only the 6.3~testoverlayfs SquashFS delta is installed 0.809
# 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.739
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.478
When the network is plugged 0.101
And Tor is ready 51.334
Then the Upgrader considers the system as up-to-date 0.392
# 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 30.944
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.970
After features/support/hooks.rb:330 0.726
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
54.543
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 15.430
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.477
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.349
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 29.121
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.957
After features/support/hooks.rb:330 1.253
After features/support/hooks.rb:100 0.000