Project Number Date
test_Tails_ISO_stable 5685 29 May 2025, 12:49

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:42.321 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:7.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 32.295
When I start Tails from USB drive "old" with network unplugged 1:30.188
Then the boot device has safe access rights 2.967
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 3.515
After features/support/hooks.rb:100 0.032
Tags: @product
2:9.269
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:27.062
Then Tails is running from USB drive "old" 0.391
And I create a persistent partition 30.764
And I take note of which tps features are available 1.598
Then a Tails persistence partition exists on USB drive "old" 0.868
And I shutdown Tails and wait for the computer to power off 8.402
After features/support/hooks.rb:330 0.201
After features/support/hooks.rb:100 0.012
Tags: @product
2:50.370
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.173
Then Tails is running from USB drive "old" 0.449
And all tps features are active 1.868
When I write some files expected to persist 1.807
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.852
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 4.346
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.618
After features/support/hooks.rb:330 0.097
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.923
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 without a persistent partition and stopped at Tails Greeter's login screen 10.456
And I log in to a new session 23.593
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.125
And I plug USB drive "to_upgrade" 2.522
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.142
Then the running Tails is installed on USB drive "to_upgrade" 22.631
And I unplug USB drive "to_upgrade" 0.253
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:330 2.019
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.384
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.584
Then all tps features from the old Tails version are active 1.811
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 3.462
And the expected persistent files created with the old Tails version are present in the filesystem 1.437
And all persistent directories from the old Tails version have safe access rights 2.519
After features/support/hooks.rb:330 1.542
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:3.828
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 11.533
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.069
And Tor is ready 48.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.598
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.211
Given I shutdown Tails and wait for the computer to power off 11.082
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.093
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.137
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.362
# 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.345
When the network is plugged 0.070
And Tor is ready 20.034
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.428
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.150
Given I shutdown Tails and wait for the computer to power off 4.382
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.518
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.816
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.267
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.057
And Tor is ready 15.916
Then the Upgrader considers the system as up-to-date 0.385
# 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.414
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.900
After features/support/hooks.rb:330 0.843
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
38.750
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 10.201
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.483
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.530
After features/support/hooks.rb:330 0.691
After features/support/hooks.rb:100 0.000