Project Number Date
test_Tails_ISO_devel 3852 03 Jun 2025, 15:12

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 22:22.944 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:35.696
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 36.832
When I start Tails from USB drive "old" with network unplugged 1:52.913
Then the boot device has safe access rights 3.537
And Tails is running from USB drive "old" 0.386
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 3.790
After features/support/hooks.rb:100 0.010
Tags: @product
2:19.817
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:32.193
Then Tails is running from USB drive "old" 0.385
And I create a persistent partition 35.136
And I take note of which tps features are available 2.242
Then a Tails persistence partition exists on USB drive "old" 0.840
And I shutdown Tails and wait for the computer to power off 8.810
After features/support/hooks.rb:330 0.173
After features/support/hooks.rb:100 0.009
Tags: @product
3:44.534
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:59.423
Then Tails is running from USB drive "old" 0.444
And all tps features are active 5.959
When I write some files expected to persist 1.779
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.413
And I take note of which tps features are available 1.439
And I shutdown Tails and wait for the computer to power off 6.650
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.537
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
3:11.842
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 33.164
And I log in to a new session 20.514
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.292
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.870
Then the running Tails is installed on USB drive "to_upgrade" 32.087
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 2.454
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.307
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.356
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.528
Then all tps features from the old Tails version are active 1.984
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 3.732
And the expected persistent files created with the old Tails version are present in the filesystem 1.575
And all persistent directories from the old Tails version have safe access rights 2.760
After features/support/hooks.rb:330 1.291
After features/support/hooks.rb:100 0.008
7:20.864
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 17.890
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.481
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.513
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.512
When the network is plugged 0.083
And Tor is ready 23.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.827
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.861
Given I shutdown Tails and wait for the computer to power off 12.757
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.991
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 3.440
And the file system changes introduced in version 6.2~testoverlayfs are present 0.385
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.375
# 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.311
When the network is plugged 0.070
And Tor is ready 18.560
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.905
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.933
Given I shutdown Tails and wait for the computer to power off 7.107
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.316
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.190
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.359
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.396
When the network is plugged 0.080
And Tor is ready 22.421
Then the Upgrader considers the system as up-to-date 0.314
# 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 16.841
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.219
After features/support/hooks.rb:330 0.754
After features/support/hooks.rb:100 0.017
44.881
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.184
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.047
And the signing key used by the Upgrader is outdated 0.135
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 23.892
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.035
After features/support/hooks.rb:330 1.899
After features/support/hooks.rb:100 0.000