Project Number Date
test_Tails_ISO_stable 5389 12 Jan 2025, 12:24

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:22.787 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
1:54.527
Before features/support/hooks.rb:269 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 27.876
When I start Tails from USB drive "old" with network unplugged 1:21.578
Then the boot device has safe access rights 2.856
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 6.963
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.042
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:21.042
Then Tails is running from USB drive "old" 0.403
And I create a persistent partition 31.009
And I take note of which tps features are available 1.317
Then a Tails persistence partition exists on USB drive "old" 0.795
And I shutdown Tails and wait for the computer to power off 6.292
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.584
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.271
Then Tails is running from USB drive "old" 0.320
And all tps features are active 1.827
When I write some files expected to persist 1.827
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.529
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.282
And I take note of which tps features are available 0.438
And I shutdown Tails and wait for the computer to power off 4.323
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.164
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.144
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 10.472
And I log in to a new session 19.171
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.639
And I plug USB drive "to_upgrade" 2.495
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.509
Then the running Tails is installed on USB drive "to_upgrade" 23.422
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:326 2.268
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.263
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.293
Then all tps features from the old Tails version are active 1.634
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 2.970
And the expected persistent files created with the old Tails version are present in the filesystem 1.472
And all persistent directories from the old Tails version have safe access rights 2.379
After features/support/hooks.rb:326 0.922
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:17.144
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.823
And no SquashFS delta is installed 0.541
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.063
And Tor is ready 19.367
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.355
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.690
Given I shutdown Tails and wait for the computer to power off 8.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.004
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.136
And the file system changes introduced in version 6.2~testoverlayfs are present 0.474
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.392
# 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.258
When the network is plugged 0.066
And Tor is ready 17.650
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.423
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.827
Given I shutdown Tails and wait for the computer to power off 4.251
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.524
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.106
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.364
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.085
And Tor is ready 16.571
Then the Upgrader considers the system as up-to-date 0.391
# 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.298
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.955
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.080
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.268
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 21.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.068
After features/support/hooks.rb:326 0.662
After features/support/hooks.rb:100 0.000