Project Number Date
test_Tails_ISO_stable 5458 14 Feb 2025, 13: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 20:37.419 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:12.429
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 34.295
When I start Tails from USB drive "old" with network unplugged 1:32.766
Then the boot device has safe access rights 2.978
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:326 3.517
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.780
Before features/support/hooks.rb:269 0.008
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:26.059
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 36.730
And I take note of which tps features are available 1.754
Then a Tails persistence partition exists on USB drive "old" 0.850
And I shutdown Tails and wait for the computer to power off 8.809
After features/support/hooks.rb:326 0.290
After features/support/hooks.rb:100 0.010
Tags: @product
2:56.898
Before features/support/hooks.rb:269 0.006
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.352
Then Tails is running from USB drive "old" 0.392
And all tps features are active 2.287
When I write some files expected to persist 1.833
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.433
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 4.376
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.783
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.012
Tags: @product
2:31.311
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.181
And I log in to a new session 18.774
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.455
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.825
Then the running Tails is installed on USB drive "to_upgrade" 24.240
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:326 2.462
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.415
Before features/support/hooks.rb:269 0.007
Given a computer 0.238
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.574
Then all tps features from the old Tails version are active 1.743
And Tails is running from USB drive "to_upgrade" 0.408
And the boot device has safe access rights 3.554
And the expected persistent files created with the old Tails version are present in the filesystem 1.420
And all persistent directories from the old Tails version have safe access rights 3.474
After features/support/hooks.rb:326 0.759
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:42.206
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.236
And no SquashFS delta is installed 0.279
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.062
And Tor is ready 20.188
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.598
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.294
Given I shutdown Tails and wait for the computer to power off 1:19.120
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.849
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.183
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.317
When the network is plugged 0.075
And Tor is ready 21.120
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.251
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.927
Given I shutdown Tails and wait for the computer to power off 4.217
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.914
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.262
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
And only the 6.3~testoverlayfs SquashFS delta is installed 0.186
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.071
And Tor is ready 19.588
Then the Upgrader considers the system as up-to-date 10.803
# 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.581
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.939
After features/support/hooks.rb:326 0.783
After features/support/hooks.rb:100 0.053
Tags: @product @automatic_upgrade
36.377
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.830
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.433
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 18.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.292
After features/support/hooks.rb:326 1.225
After features/support/hooks.rb:100 0.000