Project Number Date
test_Tails_ISO_devel 3698 17 Feb 2025, 17:34

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 18:46.934 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:2.338
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.685
When I start Tails from USB drive "old" with network unplugged 1:25.107
Then the boot device has safe access rights 3.169
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.346
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 7.071
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.222
Before features/support/hooks.rb:269 0.004
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login 1:19.815
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 32.593
And I take note of which tps features are available 1.273
Then a Tails persistence partition exists on USB drive "old" 0.815
And I shutdown Tails and wait for the computer to power off 8.261
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.477
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.686
Then Tails is running from USB drive "old" 0.455
And all tps features are active 1.910
When I write some files expected to persist 1.810
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 3.843
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.299
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.159
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.336
Before features/support/hooks.rb:269 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 11.911
And I log in to a new session 19.628
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.960
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.072
Then the running Tails is installed on USB drive "to_upgrade" 20.857
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:326 2.541
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.928
Before features/support/hooks.rb:269 0.007
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.652
Then all tps features from the old Tails version are active 1.589
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.266
And the expected persistent files created with the old Tails version are present in the filesystem 1.524
And all persistent directories from the old Tails version have safe access rights 2.394
After features/support/hooks.rb:326 0.642
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:28.880
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.272
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.066
And Tor is ready 21.922
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.109
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.044
Given I shutdown Tails and wait for the computer to power off 8.936
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.134
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.302
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.328
When the network is plugged 0.063
And Tor is ready 19.469
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.605
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.942
Given I shutdown Tails and wait for the computer to power off 4.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.232
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.025
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.255
When the network is plugged 0.082
And Tor is ready 19.202
Then the Upgrader considers the system as up-to-date 0.296
# 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 14.336
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.052
After features/support/hooks.rb:326 0.800
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.751
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.910
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 20.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.470
After features/support/hooks.rb:326 0.838
After features/support/hooks.rb:100 0.000