Project Number Date
test_Tails_ISO_devel 3802 06 May 2025, 13:38

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 23:23.750 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
3:13.643
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.302
And I create a 7200 MiB disk named "old" 0.085
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 1:13.614
When I start Tails from USB drive "old" with network unplugged 1:53.884
Then the boot device has safe access rights 3.451
And Tails is running from USB drive "old" 0.453
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.360
And I unplug USB drive "old" 0.232
After features/support/hooks.rb:330 10.933
After features/support/hooks.rb:100 0.030
Tags: @product
2:20.332
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 1.096
And I start Tails from USB drive "old" with network unplugged and I login 1:33.937
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 32.627
And I take note of which tps features are available 2.644
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.850
After features/support/hooks.rb:330 0.188
After features/support/hooks.rb:100 0.012
Tags: @product
3:32.290
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.540
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:52.055
Then Tails is running from USB drive "old" 0.576
And all tps features are active 2.979
When I write some files expected to persist 2.106
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.334
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.661
And I take note of which tps features are available 0.725
And I shutdown Tails and wait for the computer to power off 4.508
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.368
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.012
Tags: @product
2:56.747
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 20.239
And I log in to a new session 21.962
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.069
And I plug USB drive "to_upgrade" 2.645
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.481
Then the running Tails is installed on USB drive "to_upgrade" 26.769
And I unplug USB drive "to_upgrade" 0.295
And I unplug USB drive "__internal" 0.282
After features/support/hooks.rb:330 7.500
After features/support/hooks.rb:100 0.000
Tags: @product
2:40.176
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.879
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:28.707
Then all tps features from the old Tails version are active 2.036
And Tails is running from USB drive "to_upgrade" 0.394
And the boot device has safe access rights 3.529
And the expected persistent files created with the old Tails version are present in the filesystem 1.757
And all persistent directories from the old Tails version have safe access rights 2.870
After features/support/hooks.rb:330 1.514
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:54.216
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.932
And no SquashFS delta is installed 0.905
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.404
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.368
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.072
And Tor is ready 53.062
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.702
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.560
Given I shutdown Tails and wait for the computer to power off 13.316
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.804
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.627
And the file system changes introduced in version 6.2~testoverlayfs are present 0.385
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.498
When the network is plugged 0.203
And Tor is ready 19.720
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.614
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.209
Given I shutdown Tails and wait for the computer to power off 7.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:29.149
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 3.395
And the file system changes introduced in version 6.3~testoverlayfs are present 0.552
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.085
And Tor is ready 18.214
Then the Upgrader considers the system as up-to-date 0.402
# 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.380
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.576
After features/support/hooks.rb:330 0.875
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
46.343
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 12.610
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.070
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 26.159
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.241
After features/support/hooks.rb:330 1.964
After features/support/hooks.rb:100 0.000