Project Number Date
test_Tails_ISO_stable 5631 07 May 2025, 13:20

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:34.889 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:16.669
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 32.279
When I start Tails from USB drive "old" with network unplugged 1:38.750
Then the boot device has safe access rights 3.272
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:330 7.719
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.342
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:32.703
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 32.546
And I take note of which tps features are available 2.094
Then a Tails persistence partition exists on USB drive "old" 0.845
And I shutdown Tails and wait for the computer to power off 8.529
After features/support/hooks.rb:330 0.183
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.692
Then Tails is running from USB drive "old" 0.389
And all tps features are active 2.350
When I write some files expected to persist 2.023
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 3.118
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.795
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.678
After features/support/hooks.rb:330 0.108
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.166
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 11.459
And I log in to a new session 20.597
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.495
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.049
Then the running Tails is installed on USB drive "to_upgrade" 25.710
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 2.138
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.136
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.947
Then all tps features from the old Tails version are active 1.756
And Tails is running from USB drive "to_upgrade" 0.402
And the boot device has safe access rights 3.364
And the expected persistent files created with the old Tails version are present in the filesystem 1.624
And all persistent directories from the old Tails version have safe access rights 2.827
After features/support/hooks.rb:330 1.449
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:17.276
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 with a persistent partition enabled and logged in 12.903
And no SquashFS delta is installed 1.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.540
When the network is plugged 0.080
And Tor is ready 23.973
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.415
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.460
Given I shutdown Tails and wait for the computer to power off 9.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.358
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.205
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# 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.256
When the network is plugged 0.087
And Tor is ready 48.444
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.659
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.745
Given I shutdown Tails and wait for the computer to power off 4.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.549
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.477
And the file system changes introduced in version 6.3~testoverlayfs are present 0.571
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.424
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.351
When the network is plugged 0.077
And Tor is ready 18.241
Then the Upgrader considers the system as up-to-date 0.404
# 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.980
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.748
After features/support/hooks.rb:330 0.756
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.947
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 with a persistent partition enabled and logged in 10.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.510
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the signing key used by the Upgrader is outdated 0.111
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 19.847
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.194
After features/support/hooks.rb:330 0.745
After features/support/hooks.rb:100 0.000