Project Number Date
test_Tails_ISO_stable 5618 30 Apr 2025, 15:54

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 22:30.112 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:30.347
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 32.683
When I start Tails from USB drive "old" with network unplugged 1:52.313
Then the boot device has safe access rights 2.997
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:330 3.715
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.085
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:29.381
Then Tails is running from USB drive "old" 0.418
And I create a persistent partition 33.236
And I take note of which tps features are available 2.680
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.356
After features/support/hooks.rb:330 0.140
After features/support/hooks.rb:100 0.010
Tags: @product
3:8.841
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.311
Then Tails is running from USB drive "old" 1.094
And all tps features are active 2.421
When I write some files expected to persist 1.799
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.657
And I take note of which tps features are available 0.529
And I shutdown Tails and wait for the computer to power off 4.276
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.847
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.827
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 without a persistent partition and stopped at Tails Greeter's login screen 15.680
And I log in to a new session 21.076
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.786
And I plug USB drive "to_upgrade" 2.537
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.947
Then the running Tails is installed on USB drive "to_upgrade" 20.384
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 2.371
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.692
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.617
Then all tps features from the old Tails version are active 1.835
And Tails is running from USB drive "to_upgrade" 0.374
And the boot device has safe access rights 3.544
And the expected persistent files created with the old Tails version are present in the filesystem 1.479
And all persistent directories from the old Tails version have safe access rights 2.628
After features/support/hooks.rb:330 1.727
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
8:48.368
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 with a persistent partition enabled and logged in 15.561
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.196
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.121
And Tor is ready 21.745
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.981
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.926
Given I shutdown Tails and wait for the computer to power off 1:28.151
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.220
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.863
And the file system changes introduced in version 6.2~testoverlayfs are present 0.398
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.439
# 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.348
When the network is plugged 0.106
And Tor is ready 48.622
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.653
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.739
Given I shutdown Tails and wait for the computer to power off 4.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.679
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.487
And the file system changes introduced in version 6.3~testoverlayfs are present 0.660
And only the 6.3~testoverlayfs SquashFS delta is installed 0.111
# 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.354
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.331
When the network is plugged 0.083
And Tor is ready 20.461
Then the Upgrader considers the system as up-to-date 0.425
# 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 16.014
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.778
After features/support/hooks.rb:330 1.626
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
44.950
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.314
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the signing key used by the Upgrader is outdated 0.132
But a current signing key is available on our website 0.000
When the network is plugged 0.198
And Tor is ready 19.092
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.751
After features/support/hooks.rb:330 1.680
After features/support/hooks.rb:100 0.000