Project Number Date
test_Tails_ISO_stable 5426 28 Jan 2025, 14:48

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:15.450 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:29.320
Before features/support/hooks.rb:269 0.005
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 29.740
When I start Tails from USB drive "old" with network unplugged 1:53.473
Then the boot device has safe access rights 3.600
And Tails is running from USB drive "old" 0.434
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:326 3.851
After features/support/hooks.rb:100 0.007
Tags: @product
2:25.812
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:31.921
Then Tails is running from USB drive "old" 0.417
And I create a persistent partition 38.412
And I take note of which tps features are available 4.178
Then a Tails persistence partition exists on USB drive "old" 1.446
And I shutdown Tails and wait for the computer to power off 9.245
After features/support/hooks.rb:326 0.216
After features/support/hooks.rb:100 0.008
Tags: @product
3:2.203
Before features/support/hooks.rb:269 0.004
Given a computer 1.907
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.568
Then Tails is running from USB drive "old" 1.087
And all tps features are active 2.509
When I write some files expected to persist 2.585
# 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.450
And all persistent directories from the old Tails version have safe access rights 2.817
And I take note of which tps features are available 0.501
And I shutdown Tails and wait for the computer to power off 4.260
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.273
After features/support/hooks.rb:326 0.268
After features/support/hooks.rb:100 0.012
Tags: @product
2:40.287
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 12.022
And I log in to a new session 20.545
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.768
And I plug USB drive "to_upgrade" 2.460
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.107
Then the running Tails is installed on USB drive "to_upgrade" 25.937
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 3.634
After features/support/hooks.rb:100 0.000
Tags: @product
2:39.385
Before features/support/hooks.rb:269 0.009
Given a computer 0.281
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.957
Then all tps features from the old Tails version are active 4.557
And Tails is running from USB drive "to_upgrade" 0.375
And the boot device has safe access rights 3.722
And the expected persistent files created with the old Tails version are present in the filesystem 1.570
And all persistent directories from the old Tails version have safe access rights 2.920
After features/support/hooks.rb:326 0.909
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:18.649
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.477
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.103
And Tor is ready 49.493
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.874
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.214
Given I shutdown Tails and wait for the computer to power off 13.703
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.644
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.017
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.310
When the network is plugged 0.095
And Tor is ready 19.926
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.157
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.507
Given I shutdown Tails and wait for the computer to power off 6.622
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.765
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.645
And the file system changes introduced in version 6.3~testoverlayfs are present 0.599
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.374
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.341
When the network is plugged 0.089
And Tor is ready 17.208
Then the Upgrader considers the system as up-to-date 0.325
# 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.275
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.886
After features/support/hooks.rb:326 0.884
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.791
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.714
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.146
But a current signing key is available on our website 0.000
When the network is plugged 0.098
And Tor is ready 21.079
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.315
After features/support/hooks.rb:326 0.896
After features/support/hooks.rb:100 0.000