Project Number Date
test_Tails_ISO_stable 5515 14 Mar 2025, 13:11

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.134 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.366
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.914
When I start Tails from USB drive "old" with network unplugged 1:37.020
Then the boot device has safe access rights 3.146
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:330 6.852
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.595
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:39.921
Then Tails is running from USB drive "old" 0.384
And I create a persistent partition 32.323
And I take note of which tps features are available 1.416
Then a Tails persistence partition exists on USB drive "old" 0.912
And I shutdown Tails and wait for the computer to power off 8.442
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.415
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.113
Then Tails is running from USB drive "old" 0.733
And all tps features are active 2.538
When I write some files expected to persist 2.723
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.541
And I take note of which tps features are available 0.475
And I shutdown Tails and wait for the computer to power off 4.375
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.037
After features/support/hooks.rb:330 0.104
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.007
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 10.341
And I log in to a new session 19.841
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.963
And I plug USB drive "to_upgrade" 2.470
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.552
Then the running Tails is installed on USB drive "to_upgrade" 22.385
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:330 1.943
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.832
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.528
And the boot device has safe access rights 4.588
And the expected persistent files created with the old Tails version are present in the filesystem 1.567
And all persistent directories from the old Tails version have safe access rights 2.836
After features/support/hooks.rb:330 1.321
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:17.494
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 11.368
And no SquashFS delta is installed 0.242
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.502
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.180
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.552
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.554
When the network is plugged 0.087
And Tor is ready 23.615
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.066
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.134
Given I shutdown Tails and wait for the computer to power off 11.029
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.176
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.567
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.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.485
When the network is plugged 0.074
And Tor is ready 19.769
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.269
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.530
Given I shutdown Tails and wait for the computer to power off 4.471
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.234
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.160
And the file system changes introduced in version 6.3~testoverlayfs are present 0.548
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.279
When the network is plugged 0.097
And Tor is ready 47.662
Then the Upgrader considers the system as up-to-date 0.316
# 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.348
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.004
After features/support/hooks.rb:330 0.702
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.967
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 9.785
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 21.753
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.903
After features/support/hooks.rb:330 0.795
After features/support/hooks.rb:100 0.000