Project Number Date
test_Tails_ISO_devel 3702 20 Feb 2025, 09:40

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:8.740 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:16.051
Before features/support/hooks.rb:269 0.006
Given a computer 0.252
And I create a 7200 MiB disk named "old" 0.437
And I plug USB drive "old" 1.167
And I write an old version of the Tails USB image to disk "old" 35.444
When I start Tails from USB drive "old" with network unplugged 1:34.380
Then the boot device has safe access rights 3.322
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.766
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.735
Before features/support/hooks.rb:269 0.007
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:43.459
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 34.207
And I take note of which tps features are available 1.589
Then a Tails persistence partition exists on USB drive "old" 0.921
And I shutdown Tails and wait for the computer to power off 8.982
After features/support/hooks.rb:326 0.293
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.850
Before features/support/hooks.rb:269 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.754
Then Tails is running from USB drive "old" 0.372
And all tps features are active 2.011
When I write some files expected to persist 2.127
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.586
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 4.422
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.233
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.425
Before features/support/hooks.rb:269 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 10.835
And I log in to a new session 19.632
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.701
And I plug USB drive "to_upgrade" 2.429
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.599
Then the running Tails is installed on USB drive "to_upgrade" 19.759
And I unplug USB drive "to_upgrade" 0.253
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 3.542
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.091
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.116
Then all tps features from the old Tails version are active 1.711
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.511
And the expected persistent files created with the old Tails version are present in the filesystem 1.582
And all persistent directories from the old Tails version have safe access rights 2.625
After features/support/hooks.rb:326 0.636
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:50.241
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.816
And no SquashFS delta is installed 0.720
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.491
When the network is plugged 0.064
And Tor is ready 24.526
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.728
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.193
Given I shutdown Tails and wait for the computer to power off 11.006
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.306
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.289
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# 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.309
When the network is plugged 0.122
And Tor is ready 19.771
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.626
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.948
Given I shutdown Tails and wait for the computer to power off 4.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.675
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.350
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.073
And Tor is ready 16.824
Then the Upgrader considers the system as up-to-date 0.303
# 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.060
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.753
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.343
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 20.567
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.178
After features/support/hooks.rb:326 1.135
After features/support/hooks.rb:100 0.000