Project Number Date
test_Tails_ISO_stable 5513 13 Mar 2025, 13:21

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:2.249 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:14.112
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.316
And I create a 7200 MiB disk named "old" 0.134
And I plug USB drive "old" 1.080
And I write an old version of the Tails USB image to disk "old" 33.792
When I start Tails from USB drive "old" with network unplugged 1:34.136
Then the boot device has safe access rights 3.539
And Tails is running from USB drive "old" 0.410
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 3.577
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.942
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.304
And I start Tails from USB drive "old" with network unplugged and I login 1:31.997
Then Tails is running from USB drive "old" 0.403
And I create a persistent partition 30.695
And I take note of which tps features are available 1.850
Then a Tails persistence partition exists on USB drive "old" 0.904
And I shutdown Tails and wait for the computer to power off 8.785
After features/support/hooks.rb:330 0.231
After features/support/hooks.rb:100 0.011
Tags: @product
2:59.787
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.337
Then Tails is running from USB drive "old" 1.254
And all tps features are active 2.248
When I write some files expected to persist 1.728
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.740
And I take note of which tps features are available 0.778
And I shutdown Tails and wait for the computer to power off 4.660
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.187
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.009
Tags: @product
2:43.518
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.285
And I log in to a new session 21.501
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.833
And I plug USB drive "to_upgrade" 2.491
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.944
Then the running Tails is installed on USB drive "to_upgrade" 24.028
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:330 2.970
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.283
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.246
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.086
Then all tps features from the old Tails version are active 1.873
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 3.652
And the expected persistent files created with the old Tails version are present in the filesystem 1.521
And all persistent directories from the old Tails version have safe access rights 2.514
After features/support/hooks.rb:330 0.686
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:47.575
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.864
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.475
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.370
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.084
And Tor is ready 20.931
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.186
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.926
Given I shutdown Tails and wait for the computer to power off 11.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.955
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.310
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.305
When the network is plugged 0.136
And Tor is ready 19.554
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.655
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.145
Given I shutdown Tails and wait for the computer to power off 4.332
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.445
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.383
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.087
And Tor is ready 18.127
Then the Upgrader considers the system as up-to-date 0.299
# 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.127
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.961
After features/support/hooks.rb:330 0.831
After features/support/hooks.rb:100 0.040
Tags: @product @automatic_upgrade
37.030
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 9.978
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.527
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.142
And the signing key used by the Upgrader is outdated 0.143
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 20.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.235
After features/support/hooks.rb:330 0.725
After features/support/hooks.rb:100 0.000