Project Number Date
test_Tails_ISO_devel 3848 02 Jun 2025, 13:08

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 20:22.004 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:17.738
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.891
When I start Tails from USB drive "old" with network unplugged 1:40.489
Then the boot device has safe access rights 3.098
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 7.288
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.404
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 1:25.049
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 32.824
And I take note of which tps features are available 1.774
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 8.396
After features/support/hooks.rb:330 0.193
After features/support/hooks.rb:100 0.008
Tags: @product
2:49.999
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.692
Then Tails is running from USB drive "old" 0.522
And all tps features are active 2.097
When I write some files expected to persist 1.741
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.873
And I take note of which tps features are available 0.406
And I shutdown Tails and wait for the computer to power off 4.184
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.637
After features/support/hooks.rb:330 0.136
After features/support/hooks.rb:100 0.008
Tags: @product
2:46.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.177
And I log in to a new session 21.119
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.107
And I plug USB drive "to_upgrade" 2.562
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.269
Then the running Tails is installed on USB drive "to_upgrade" 27.500
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 2.406
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.354
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.716
Then all tps features from the old Tails version are active 1.571
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.465
And the expected persistent files created with the old Tails version are present in the filesystem 1.600
And all persistent directories from the old Tails version have safe access rights 2.448
After features/support/hooks.rb:330 1.070
After features/support/hooks.rb:100 0.099
Tags: @product @automatic_upgrade
7:2.320
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 12.905
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.531
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.529
When the network is plugged 0.097
And Tor is ready 23.368
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.768
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.396
Given I shutdown Tails and wait for the computer to power off 10.907
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.826
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 1.981
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.316
When the network is plugged 0.069
And Tor is ready 46.051
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.631
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.609
Given I shutdown Tails and wait for the computer to power off 4.508
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.307
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.977
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.389
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.073
And Tor is ready 18.840
Then the Upgrader considers the system as up-to-date 0.313
# 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 15.343
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.518
After features/support/hooks.rb:330 0.869
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
56.041
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.771
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.463
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 0.114
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 44.951
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.580
After features/support/hooks.rb:330 0.943
After features/support/hooks.rb:100 0.000