Project Number Date
test_Tails_ISO_stable 5475 21 Feb 2025, 12:44

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 19:18.498 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:4.587
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 33.639
When I start Tails from USB drive "old" with network unplugged 1:25.458
Then the boot device has safe access rights 3.199
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 7.084
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.749
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:24.543
Then Tails is running from USB drive "old" 0.395
And I create a persistent partition 33.286
And I take note of which tps features are available 1.428
Then a Tails persistence partition exists on USB drive "old" 0.963
And I shutdown Tails and wait for the computer to power off 8.941
After features/support/hooks.rb:326 0.229
After features/support/hooks.rb:100 0.010
Tags: @product
2:48.113
Before features/support/hooks.rb:269 0.007
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.330
Then Tails is running from USB drive "old" 0.657
And all tps features are active 2.147
When I write some files expected to persist 1.866
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.364
And all persistence configuration files have safe access rights 0.950
And all persistent directories from the old Tails version have safe access rights 2.623
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 4.807
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.717
After features/support/hooks.rb:326 0.122
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.530
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 11.523
And I log in to a new session 18.752
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.791
And I plug USB drive "to_upgrade" 2.569
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.172
Then the running Tails is installed on USB drive "to_upgrade" 18.321
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 7.091
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.655
Before features/support/hooks.rb:269 0.009
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.080
Then all tps features from the old Tails version are active 1.814
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 3.245
And the expected persistent files created with the old Tails version are present in the filesystem 1.489
And all persistent directories from the old Tails version have safe access rights 2.506
After features/support/hooks.rb:326 0.667
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:45.366
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.466
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.075
And Tor is ready 50.133
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.582
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.983
Given I shutdown Tails and wait for the computer to power off 8.795
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.145
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.116
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.373
When the network is plugged 0.065
And Tor is ready 20.262
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.355
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.081
Given I shutdown Tails and wait for the computer to power off 4.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.276
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.508
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.066
And Tor is ready 18.896
Then the Upgrader considers the system as up-to-date 0.322
# 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.708
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.082
After features/support/hooks.rb:326 0.725
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.494
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.257
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 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.073
And Tor is ready 21.841
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.685
After features/support/hooks.rb:326 0.688
After features/support/hooks.rb:100 0.000