Project Number Date
test_Tails_ISO_devel 3734 12 Mar 2025, 11:23

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 21:50.558 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:37.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 37.493
When I start Tails from USB drive "old" with network unplugged 1:54.630
Then the boot device has safe access rights 3.300
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.262
After features/support/hooks.rb:330 3.628
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.535
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:31.086
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 33.014
And I take note of which tps features are available 2.049
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 10.014
After features/support/hooks.rb:330 0.241
After features/support/hooks.rb:100 0.013
Tags: @product
3:6.644
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.281
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.289
Then Tails is running from USB drive "old" 0.397
And all tps features are active 2.303
When I write some files expected to persist 2.474
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.323
And all persistence configuration files have safe access rights 0.477
And all persistent directories from the old Tails version have safe access rights 2.879
And I take note of which tps features are available 0.562
And I shutdown Tails and wait for the computer to power off 4.436
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.217
After features/support/hooks.rb:330 0.181
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.575
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 11.873
And I log in to a new session 20.976
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.020
And I plug USB drive "to_upgrade" 2.497
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.707
Then the running Tails is installed on USB drive "to_upgrade" 26.079
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 4.857
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.300
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.314
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.135
Then all tps features from the old Tails version are active 1.808
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 4.148
And the expected persistent files created with the old Tails version are present in the filesystem 1.660
And all persistent directories from the old Tails version have safe access rights 2.854
After features/support/hooks.rb:330 1.208
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:4.166
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 14.096
And no SquashFS delta is installed 0.583
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.443
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.124
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.074
And Tor is ready 25.067
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.780
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.694
Given I shutdown Tails and wait for the computer to power off 10.936
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.865
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 6.369
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.291
When the network is plugged 0.608
And Tor is ready 19.797
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.141
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.994
Given I shutdown Tails and wait for the computer to power off 1:10.604
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.382
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.435
And the file system changes introduced in version 6.3~testoverlayfs are present 0.610
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.319
When the network is plugged 0.367
And Tor is ready 17.280
Then the Upgrader considers the system as up-to-date 0.444
# 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.789
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.211
After features/support/hooks.rb:330 1.041
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
41.540
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 14.139
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.862
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.132
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 20.738
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.499
After features/support/hooks.rb:330 0.903
After features/support/hooks.rb:100 0.000