Project Number Date
test_Tails_ISO_stable 5552 03 Apr 2025, 20:50

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.429 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:6.761
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.875
When I start Tails from USB drive "old" with network unplugged 1:30.543
Then the boot device has safe access rights 3.063
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:330 3.777
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.133
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:21.367
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 30.792
And I take note of which tps features are available 2.241
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.435
After features/support/hooks.rb:330 0.192
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.741
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.320
Then Tails is running from USB drive "old" 0.460
And all tps features are active 1.901
When I write some files expected to persist 1.824
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.489
And all persistent directories from the old Tails version have safe access rights 2.613
And I take note of which tps features are available 0.406
And I shutdown Tails and wait for the computer to power off 4.402
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.884
After features/support/hooks.rb:330 0.118
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.712
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 10.062
And I log in to a new session 18.833
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.937
And I plug USB drive "to_upgrade" 2.533
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.892
Then the running Tails is installed on USB drive "to_upgrade" 25.059
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:330 1.024
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.892
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.582
Then all tps features from the old Tails version are active 1.555
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.382
And the expected persistent files created with the old Tails version are present in the filesystem 1.446
And all persistent directories from the old Tails version have safe access rights 2.414
After features/support/hooks.rb:330 1.176
After features/support/hooks.rb:100 0.011
6:42.290
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.002
And no SquashFS delta is installed 0.547
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.067
And Tor is ready 21.863
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.969
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.199
Given I shutdown Tails and wait for the computer to power off 10.794
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.397
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.022
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.377
When the network is plugged 0.082
And Tor is ready 15.762
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.957
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.350
Given I shutdown Tails and wait for the computer to power off 4.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.140
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.201
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.389
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.364
When the network is plugged 0.072
And Tor is ready 19.025
Then the Upgrader considers the system as up-to-date 0.312
# 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.033
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.529
After features/support/hooks.rb:330 0.731
After features/support/hooks.rb:100 0.017
37.896
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.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.792
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 20.379
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.531
After features/support/hooks.rb:330 0.959
After features/support/hooks.rb:100 0.000