Project Number Date
test_Tails_ISO_devel 3834 25 May 2025, 09:51

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:8.777 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:11.673
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.498
When I start Tails from USB drive "old" with network unplugged 1:33.516
Then the boot device has safe access rights 3.342
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:330 3.761
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.682
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.323
And I start Tails from USB drive "old" with network unplugged and I login 1:29.031
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 31.376
And I take note of which tps features are available 2.399
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 8.419
After features/support/hooks.rb:330 0.177
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.836
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.485
Then Tails is running from USB drive "old" 1.140
And all tps features are active 2.246
When I write some files expected to persist 1.847
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.370
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.519
And I take note of which tps features are available 0.532
And I shutdown Tails and wait for the computer to power off 4.711
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.350
After features/support/hooks.rb:330 0.163
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.017
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 without a persistent partition and stopped at Tails Greeter's login screen 11.194
And I log in to a new session 18.729
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.503
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.038
Then the running Tails is installed on USB drive "to_upgrade" 25.732
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 2.206
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.476
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.355
Then all tps features from the old Tails version are active 1.693
And Tails is running from USB drive "to_upgrade" 0.375
And the boot device has safe access rights 3.402
And the expected persistent files created with the old Tails version are present in the filesystem 1.859
And all persistent directories from the old Tails version have safe access rights 2.587
After features/support/hooks.rb:330 1.240
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:20.188
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 41.238
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.365
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.078
And Tor is ready 51.249
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.591
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.629
Given I shutdown Tails and wait for the computer to power off 8.616
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.346
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.034
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.281
# 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.288
When the network is plugged 0.073
And Tor is ready 20.479
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.694
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.452
Given I shutdown Tails and wait for the computer to power off 4.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.859
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.228
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.270
When the network is plugged 0.072
And Tor is ready 18.742
Then the Upgrader considers the system as up-to-date 0.390
# 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 17.007
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.602
After features/support/hooks.rb:330 0.716
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.903
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.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.080
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 21.229
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.067
After features/support/hooks.rb:330 1.061
After features/support/hooks.rb:100 0.000