Project Number Date
test_Tails_ISO_devel 3746 20 Mar 2025, 13:25

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 19:58.220 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.416
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 30.371
When I start Tails from USB drive "old" with network unplugged 1:35.417
Then the boot device has safe access rights 3.249
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 3.788
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.580
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.298
And I start Tails from USB drive "old" with network unplugged and I login 1:27.105
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 33.704
And I take note of which tps features are available 1.698
Then a Tails persistence partition exists on USB drive "old" 0.926
And I shutdown Tails and wait for the computer to power off 8.479
After features/support/hooks.rb:330 0.194
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.033
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.322
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.837
Then Tails is running from USB drive "old" 0.334
And all tps features are active 2.078
When I write some files expected to persist 1.846
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 3.120
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 6.702
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.625
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.404
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.441
And I log in to a new session 21.495
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.818
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.216
Then the running Tails is installed on USB drive "to_upgrade" 20.526
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 3.288
After features/support/hooks.rb:100 0.000
Tags: @product
2:34.703
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.254
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.913
Then all tps features from the old Tails version are active 2.244
And Tails is running from USB drive "to_upgrade" 0.414
And the boot device has safe access rights 3.401
And the expected persistent files created with the old Tails version are present in the filesystem 1.619
And all persistent directories from the old Tails version have safe access rights 2.853
After features/support/hooks.rb:330 2.145
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:53.106
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.087
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.620
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.095
And Tor is ready 22.866
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.603
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.746
Given I shutdown Tails and wait for the computer to power off 8.947
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.516
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.529
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.341
When the network is plugged 0.081
And Tor is ready 20.464
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.678
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.413
Given I shutdown Tails and wait for the computer to power off 4.433
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.497
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.215
And the file system changes introduced in version 6.3~testoverlayfs are present 0.702
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.072
And Tor is ready 21.997
Then the Upgrader considers the system as up-to-date 0.337
# 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.259
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.148
After features/support/hooks.rb:330 0.827
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
40.976
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.613
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
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.082
And Tor is ready 23.731
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.951
After features/support/hooks.rb:330 0.963
After features/support/hooks.rb:100 0.000