Project Number Date
test_Tails_ISO_devel 3865 12 Jun 2025, 13:16

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:4.073 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:15.000
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.327
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.122
And I write an old version of the Tails USB image to disk "old" 36.923
When I start Tails from USB drive "old" with network unplugged 1:32.583
Then the boot device has safe access rights 2.927
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 0.854
After features/support/hooks.rb:100 0.014
Tags: @product
2:9.361
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:27.329
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 30.201
And I take note of which tps features are available 2.154
Then a Tails persistence partition exists on USB drive "old" 0.715
And I shutdown Tails and wait for the computer to power off 8.408
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.495
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.977
Then Tails is running from USB drive "old" 0.397
And all tps features are active 2.425
When I write some files expected to persist 2.212
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.417
And I take note of which tps features are available 0.781
And I shutdown Tails and wait for the computer to power off 6.555
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.887
After features/support/hooks.rb:330 0.115
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.461
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 11.588
And I log in to a new session 19.177
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.695
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.020
Then the running Tails is installed on USB drive "to_upgrade" 26.133
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 2.381
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.934
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.435
Then all tps features from the old Tails version are active 1.654
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.272
And the expected persistent files created with the old Tails version are present in the filesystem 1.602
And all persistent directories from the old Tails version have safe access rights 2.397
After features/support/hooks.rb:330 1.264
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:11.344
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 30.386
And no SquashFS delta is installed 0.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.503
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.444
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.400
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.093
And Tor is ready 24.294
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.853
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.975
Given I shutdown Tails and wait for the computer to power off 8.971
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.925
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.197
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.334
When the network is plugged 0.077
And Tor is ready 20.898
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.841
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.011
Given I shutdown Tails and wait for the computer to power off 4.519
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.341
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.332
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.331
When the network is plugged 0.065
And Tor is ready 18.578
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.684
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.676
After features/support/hooks.rb:330 0.827
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.474
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.851
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.996
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 20.230
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.865
After features/support/hooks.rb:330 1.435
After features/support/hooks.rb:100 0.000