Project Number Date
test_Tails_ISO_devel 3825 20 May 2025, 22:01

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:36.985 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:24.766
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 33.147
When I start Tails from USB drive "old" with network unplugged 1:45.575
Then the boot device has safe access rights 3.531
And Tails is running from USB drive "old" 0.411
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:330 3.544
After features/support/hooks.rb:100 0.036
Tags: @product
2:10.467
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:26.619
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 33.381
And I take note of which tps features are available 2.624
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 6.457
After features/support/hooks.rb:330 0.209
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.147
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.287
Then Tails is running from USB drive "old" 0.451
And all tps features are active 1.947
When I write some files expected to persist 1.803
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.673
And I take note of which tps features are available 0.547
And I shutdown Tails and wait for the computer to power off 4.424
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.139
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.289
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 11.742
And I log in to a new session 21.269
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.005
And I plug USB drive "to_upgrade" 2.548
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.064
Then the running Tails is installed on USB drive "to_upgrade" 27.181
And I unplug USB drive "to_upgrade" 0.252
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 3.629
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.773
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.233
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.365
Then all tps features from the old Tails version are active 2.103
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 4.037
And the expected persistent files created with the old Tails version are present in the filesystem 1.781
And all persistent directories from the old Tails version have safe access rights 2.904
After features/support/hooks.rb:330 1.903
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
7:14.990
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.249
And no SquashFS delta is installed 0.177
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
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.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.123
And Tor is ready 21.930
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.026
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.606
Given I shutdown Tails and wait for the computer to power off 9.150
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.680
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.468
And the file system changes introduced in version 6.2~testoverlayfs are present 0.480
And only the 6.2~testoverlayfs SquashFS delta is installed 0.122
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.388
# 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.325
When the network is plugged 0.081
And Tor is ready 20.415
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.447
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.894
Given I shutdown Tails and wait for the computer to power off 4.851
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.975
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.120
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.083
And Tor is ready 20.338
Then the Upgrader considers the system as up-to-date 0.343
# 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.730
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.598
After features/support/hooks.rb:330 0.745
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
37.549
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 10.569
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.478
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.101
But a current signing key is available on our website 0.000
When the network is plugged 0.178
And Tor is ready 25.479
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.668
After features/support/hooks.rb:330 1.091
After features/support/hooks.rb:100 0.000