Project Number Date
test_Tails_ISO_stable 5494 04 Mar 2025, 22:55

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:48.705 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.469
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 30.057
When I start Tails from USB drive "old" with network unplugged 1:35.448
Then the boot device has safe access rights 3.588
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:330 6.876
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.923
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login 1:35.743
Then Tails is running from USB drive "old" 1.133
And I create a persistent partition 33.683
And I take note of which tps features are available 2.437
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 8.854
After features/support/hooks.rb:330 0.349
After features/support/hooks.rb:100 0.011
Tags: @product
3:1.838
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.434
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.344
Then Tails is running from USB drive "old" 0.428
And all tps features are active 2.696
When I write some files expected to persist 1.859
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.497
And I take note of which tps features are available 0.596
And I shutdown Tails and wait for the computer to power off 4.361
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.976
After features/support/hooks.rb:330 0.102
After features/support/hooks.rb:100 0.007
Tags: @product
2:46.939
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 without a persistent partition and stopped at Tails Greeter's login screen 24.093
And I log in to a new session 21.068
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.936
And I plug USB drive "to_upgrade" 2.449
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.625
Then the running Tails is installed on USB drive "to_upgrade" 20.357
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:330 3.364
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.608
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.236
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.600
Then all tps features from the old Tails version are active 1.850
And Tails is running from USB drive "to_upgrade" 0.454
And the boot device has safe access rights 3.627
And the expected persistent files created with the old Tails version are present in the filesystem 1.351
And all persistent directories from the old Tails version have safe access rights 2.487
After features/support/hooks.rb:330 1.331
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:31.790
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.129
And no SquashFS delta is installed 0.150
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.065
And Tor is ready 47.851
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.616
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.015
Given I shutdown Tails and wait for the computer to power off 9.004
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.751
Then Tails is running version 6.2~testoverlayfs 0.028
And all tps features are active 2.389
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.389
# 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.282
When the network is plugged 0.075
And Tor is ready 16.333
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.671
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.009
Given I shutdown Tails and wait for the computer to power off 4.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.299
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.380
And the file system changes introduced in version 6.3~testoverlayfs are present 0.574
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.385
When the network is plugged 0.090
And Tor is ready 21.454
Then the Upgrader considers the system as up-to-date 0.298
# 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.185
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.096
After features/support/hooks.rb:330 0.798
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.135
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.341
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 19.635
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.575
After features/support/hooks.rb:330 0.678
After features/support/hooks.rb:100 0.000