Project Number Date
test_Tails_ISO_devel 3805 08 May 2025, 13:06

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 22:32.891 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:36.635
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.275
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.127
And I write an old version of the Tails USB image to disk "old" 46.397
When I start Tails from USB drive "old" with network unplugged 1:44.216
Then the boot device has safe access rights 3.469
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:330 3.790
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.903
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.266
And I start Tails from USB drive "old" with network unplugged and I login 1:40.535
Then Tails is running from USB drive "old" 0.439
And I create a persistent partition 35.049
And I take note of which tps features are available 4.666
Then a Tails persistence partition exists on USB drive "old" 1.397
And I shutdown Tails and wait for the computer to power off 8.548
After features/support/hooks.rb:330 0.264
After features/support/hooks.rb:100 0.023
Tags: @product
3:26.953
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 1.612
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:38.109
Then Tails is running from USB drive "old" 1.039
And all tps features are active 4.648
When I write some files expected to persist 2.202
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.475
And all persistent directories from the old Tails version have safe access rights 3.310
And I take note of which tps features are available 1.451
And I shutdown Tails and wait for the computer to power off 7.147
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.673
After features/support/hooks.rb:330 0.154
After features/support/hooks.rb:100 0.014
Tags: @product
3:3.943
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 19.759
And I log in to a new session 21.615
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.987
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.591
Then the running Tails is installed on USB drive "to_upgrade" 33.155
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 3.703
After features/support/hooks.rb:100 0.000
Tags: @product
2:46.916
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 1.884
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:34.336
Then all tps features from the old Tails version are active 1.730
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 4.199
And the expected persistent files created with the old Tails version are present in the filesystem 1.696
And all persistent directories from the old Tails version have safe access rights 2.722
After features/support/hooks.rb:330 1.131
After features/support/hooks.rb:100 0.008
7:30.844
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 11.053
And no SquashFS delta is installed 0.096
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.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.599
When the network is plugged 0.691
And Tor is ready 22.492
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.905
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.120
Given I shutdown Tails and wait for the computer to power off 11.355
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:29.005
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.468
And the file system changes introduced in version 6.2~testoverlayfs are present 0.380
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.338
When the network is plugged 0.079
And Tor is ready 21.025
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.037
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.535
Given I shutdown Tails and wait for the computer to power off 4.512
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.261
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.280
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.419
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.357
When the network is plugged 0.078
And Tor is ready 18.934
Then the Upgrader considers the system as up-to-date 0.350
# 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.545
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.133
After features/support/hooks.rb:330 0.795
After features/support/hooks.rb:100 0.023
36.695
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.198
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 17.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.644
After features/support/hooks.rb:330 1.248
After features/support/hooks.rb:100 0.000