Project Number Date
test_Tails_ISO_stable 5622 02 May 2025, 12: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 19:22.019 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:59.117
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 30.090
When I start Tails from USB drive "old" with network unplugged 1:23.738
Then the boot device has safe access rights 3.037
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 6.855
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.885
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:23.825
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 30.965
And I take note of which tps features are available 1.474
Then a Tails persistence partition exists on USB drive "old" 0.726
And I shutdown Tails and wait for the computer to power off 8.322
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.762
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.421
Then Tails is running from USB drive "old" 0.795
And all tps features are active 2.185
When I write some files expected to persist 2.200
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.316
And I take note of which tps features are available 0.597
And I shutdown Tails and wait for the computer to power off 4.355
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.137
After features/support/hooks.rb:330 0.102
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.508
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 15.188
And I log in to a new session 17.525
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.386
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.175
Then the running Tails is installed on USB drive "to_upgrade" 21.404
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 0.896
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.884
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.593
Then all tps features from the old Tails version are active 1.703
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 3.716
And the expected persistent files created with the old Tails version are present in the filesystem 1.584
And all persistent directories from the old Tails version have safe access rights 2.712
After features/support/hooks.rb:330 1.378
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:53.346
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.867
And no SquashFS delta is installed 0.266
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.479
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.063
And Tor is ready 20.299
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.906
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.489
Given I shutdown Tails and wait for the computer to power off 8.879
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.890
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.467
And the file system changes introduced in version 6.2~testoverlayfs are present 0.360
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.428
# 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.312
When the network is plugged 0.411
And Tor is ready 16.591
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.916
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.147
Given I shutdown Tails and wait for the computer to power off 4.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.236
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.342
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.084
And Tor is ready 18.663
Then the Upgrader considers the system as up-to-date 0.330
# 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.735
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.496
After features/support/hooks.rb:330 0.794
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.514
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.417
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.510
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the signing key used by the Upgrader is outdated 0.094
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 20.979
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.324
After features/support/hooks.rb:330 0.992
After features/support/hooks.rb:100 0.000