Project Number Date
test_Tails_ISO_stable 5417 25 Jan 2025, 12:27

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 18:53.428 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:3.771
Before features/support/hooks.rb:269 0.005
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.531
When I start Tails from USB drive "old" with network unplugged 1:29.809
Then the boot device has safe access rights 3.119
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.726
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.827
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:23.068
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 31.770
And I take note of which tps features are available 1.484
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 8.183
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.017
Tags: @product
2:51.970
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.912
Then Tails is running from USB drive "old" 0.870
And all tps features are active 2.152
When I write some files expected to persist 2.066
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.295
And all persistence configuration files have safe access rights 1.004
And all persistent directories from the old Tails version have safe access rights 2.397
And I take note of which tps features are available 0.514
And I shutdown Tails and wait for the computer to power off 4.440
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.134
After features/support/hooks.rb:326 0.093
After features/support/hooks.rb:100 0.008
Tags: @product
2:23.705
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.464
And I log in to a new session 17.290
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.409
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.146
Then the running Tails is installed on USB drive "to_upgrade" 20.535
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 2.027
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.098
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.060
Then all tps features from the old Tails version are active 1.708
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.434
And the expected persistent files created with the old Tails version are present in the filesystem 1.703
And all persistent directories from the old Tails version have safe access rights 2.671
After features/support/hooks.rb:326 0.893
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:33.559
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 15.917
And no SquashFS delta is installed 0.371
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.063
And Tor is ready 22.395
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.763
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.375
Given I shutdown Tails and wait for the computer to power off 9.047
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.407
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.171
And the file system changes introduced in version 6.2~testoverlayfs are present 0.396
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.339
# 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.479
When the network is plugged 0.081
And Tor is ready 17.356
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.572
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.852
Given I shutdown Tails and wait for the computer to power off 4.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.021
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.191
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.364
When the network is plugged 0.095
And Tor is ready 17.461
Then the Upgrader considers the system as up-to-date 0.304
# 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 14.891
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.185
After features/support/hooks.rb:326 0.833
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.496
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 10.503
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.497
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 19.021
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.254
After features/support/hooks.rb:326 1.040
After features/support/hooks.rb:100 0.000