Project Number Date
test_Tails_ISO_stable 5538 30 Mar 2025, 12:39

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:58.490 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:1.077
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.289
When I start Tails from USB drive "old" with network unplugged 1:24.579
Then the boot device has safe access rights 2.942
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 6.799
After features/support/hooks.rb:100 0.009
Tags: @product
2:2.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:20.527
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 31.237
And I take note of which tps features are available 1.449
Then a Tails persistence partition exists on USB drive "old" 0.718
And I shutdown Tails and wait for the computer to power off 8.154
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.155
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.337
Then Tails is running from USB drive "old" 0.650
And all tps features are active 1.858
When I write some files expected to persist 3.050
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.343
And I take note of which tps features are available 0.383
And I shutdown Tails and wait for the computer to power off 4.620
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.109
After features/support/hooks.rb:330 0.101
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.516
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 without a persistent partition and stopped at Tails Greeter's login screen 10.409
And I log in to a new session 18.254
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.583
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.350
Then the running Tails is installed on USB drive "to_upgrade" 26.143
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:330 2.264
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.668
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.192
Then all tps features from the old Tails version are active 1.609
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 2.902
And the expected persistent files created with the old Tails version are present in the filesystem 1.327
And all persistent directories from the old Tails version have safe access rights 2.144
After features/support/hooks.rb:330 1.465
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:27.252
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 10.911
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.466
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.361
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.067
And Tor is ready 20.028
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.750
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.232
Given I shutdown Tails and wait for the computer to power off 8.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.993
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.887
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.266
# 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.317
When the network is plugged 0.068
And Tor is ready 16.284
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.756
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.598
Given I shutdown Tails and wait for the computer to power off 1:10.029
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.839
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 1.917
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.282
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.444
When the network is plugged 0.065
And Tor is ready 19.526
Then the Upgrader considers the system as up-to-date 0.321
# 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 13.821
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.982
After features/support/hooks.rb:330 0.748
After features/support/hooks.rb:100 0.046
Tags: @product @automatic_upgrade
37.192
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 9.650
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.172
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 20.588
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.260
After features/support/hooks.rb:330 0.781
After features/support/hooks.rb:100 0.000