Project Number Date
test_Tails_ISO_stable 5567 10 Apr 2025, 19:35

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:42.878 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:39.132
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.289
And I create a 7200 MiB disk named "old" 0.072
And I plug USB drive "old" 1.086
And I write an old version of the Tails USB image to disk "old" 55.686
When I start Tails from USB drive "old" with network unplugged 1:37.800
Then the boot device has safe access rights 3.152
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.370
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 7.223
After features/support/hooks.rb:100 0.010
Tags: @product
2:19.360
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 1.740
And I start Tails from USB drive "old" with network unplugged and I login 1:32.939
Then Tails is running from USB drive "old" 0.402
And I create a persistent partition 32.675
And I take note of which tps features are available 1.859
Then a Tails persistence partition exists on USB drive "old" 0.870
And I shutdown Tails and wait for the computer to power off 8.871
After features/support/hooks.rb:330 0.199
After features/support/hooks.rb:100 0.008
Tags: @product
3:9.115
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.086
Then Tails is running from USB drive "old" 0.340
And all tps features are active 2.207
When I write some files expected to persist 1.754
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.346
And all persistence configuration files have safe access rights 0.726
And all persistent directories from the old Tails version have safe access rights 2.730
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 6.417
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.738
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.460
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 10.306
And I log in to a new session 18.523
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.672
And I plug USB drive "to_upgrade" 2.606
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.624
Then the running Tails is installed on USB drive "to_upgrade" 27.294
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:330 1.529
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.254
Then all tps features from the old Tails version are active 1.634
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.623
And the expected persistent files created with the old Tails version are present in the filesystem 1.515
And all persistent directories from the old Tails version have safe access rights 2.700
After features/support/hooks.rb:330 1.479
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:56.325
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 13.001
And no SquashFS delta is installed 0.066
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.113
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.501
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.569
When the network is plugged 0.089
And Tor is ready 20.549
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.036
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.718
Given I shutdown Tails and wait for the computer to power off 11.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.300
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.424
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.337
When the network is plugged 0.086
And Tor is ready 22.272
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.222
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.436
Given I shutdown Tails and wait for the computer to power off 4.431
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.733
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.636
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.297
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.073
And Tor is ready 19.555
Then the Upgrader considers the system as up-to-date 0.338
# 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.575
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.836
After features/support/hooks.rb:330 0.881
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
48.196
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 with a persistent partition enabled and logged in 16.522
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.581
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.125
But a current signing key is available on our website 0.000
When the network is plugged 0.102
And Tor is ready 20.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.837
After features/support/hooks.rb:330 1.353
After features/support/hooks.rb:100 0.000