Project Number Date
test_Tails_ISO_stable 5451 11 Feb 2025, 22:02

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:55.596 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:9.761
Before features/support/hooks.rb:269 0.007
Given a computer 0.292
And I create a 7200 MiB disk named "old" 0.098
And I plug USB drive "old" 1.127
And I write an old version of the Tails USB image to disk "old" 36.643
When I start Tails from USB drive "old" with network unplugged 1:26.990
Then the boot device has safe access rights 3.379
And Tails is running from USB drive "old" 0.472
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.123
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 3.562
After features/support/hooks.rb:100 0.012
Tags: @product
2:19.705
Before features/support/hooks.rb:269 0.006
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 1:34.714
Then Tails is running from USB drive "old" 0.424
And I create a persistent partition 32.212
And I take note of which tps features are available 1.767
Then a Tails persistence partition exists on USB drive "old" 0.898
And I shutdown Tails and wait for the computer to power off 9.454
After features/support/hooks.rb:326 0.323
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.618
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.277
Then Tails is running from USB drive "old" 0.376
And all tps features are active 2.078
When I write some files expected to persist 2.200
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.283
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 2.582
And I take note of which tps features are available 0.584
And I shutdown Tails and wait for the computer to power off 4.294
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.281
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.011
Tags: @product
2:29.337
Before features/support/hooks.rb:269 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.826
And I log in to a new session 18.864
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.803
And I plug USB drive "to_upgrade" 2.522
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.494
Then the running Tails is installed on USB drive "to_upgrade" 17.386
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 4.433
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.947
Before features/support/hooks.rb:269 0.005
Given a computer 0.300
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.927
Then all tps features from the old Tails version are active 1.825
And Tails is running from USB drive "to_upgrade" 0.408
And the boot device has safe access rights 3.635
And the expected persistent files created with the old Tails version are present in the filesystem 1.629
And all persistent directories from the old Tails version have safe access rights 3.220
After features/support/hooks.rb:326 0.697
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:50.618
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.909
And no SquashFS delta is installed 0.245
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.096
And Tor is ready 22.471
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.451
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.287
Given I shutdown Tails and wait for the computer to power off 11.062
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.130
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.337
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.262
When the network is plugged 0.092
And Tor is ready 20.604
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.239
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.688
Given I shutdown Tails and wait for the computer to power off 6.895
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.018
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.344
And the file system changes introduced in version 6.3~testoverlayfs are present 0.636
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.335
When the network is plugged 0.078
And Tor is ready 19.422
Then the Upgrader considers the system as up-to-date 0.330
# 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.100
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.182
After features/support/hooks.rb:326 0.815
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.607
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.759
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 17.549
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.949
After features/support/hooks.rb:326 0.925
After features/support/hooks.rb:100 0.000