Project Number Date
test_Tails_ISO_devel 3898 06 Jul 2025, 13:10

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:3.882 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:22.933
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.099
And I write an old version of the Tails USB image to disk "old" 30.139
When I start Tails from USB drive "old" with network unplugged 1:45.801
Then the boot device has safe access rights 4.307
And Tails is running from USB drive "old" 0.513
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.124
And udev-watchdog is monitoring the correct device 0.438
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:330 7.453
After features/support/hooks.rb:100 0.021
Tags: @product
2:29.340
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:41.877
Then Tails is running from USB drive "old" 0.398
And I create a persistent partition 34.952
And I take note of which tps features are available 2.575
Then a Tails persistence partition exists on USB drive "old" 0.798
And I shutdown Tails and wait for the computer to power off 8.541
After features/support/hooks.rb:330 0.285
After features/support/hooks.rb:100 0.009
Tags: @product
3:24.442
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:39.808
Then Tails is running from USB drive "old" 1.483
And all tps features are active 2.157
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.240
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 2.586
And I take note of which tps features are available 0.540
And I shutdown Tails and wait for the computer to power off 6.699
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.467
After features/support/hooks.rb:330 0.096
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.751
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 without a persistent partition and stopped at Tails Greeter's login screen 12.494
And I log in to a new session 22.808
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.507
And I plug USB drive "to_upgrade" 2.500
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.089
Then the running Tails is installed on USB drive "to_upgrade" 32.530
And I unplug USB drive "to_upgrade" 0.422
And I unplug USB drive "__internal" 0.398
After features/support/hooks.rb:330 2.795
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.611
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.291
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.628
Then all tps features from the old Tails version are active 2.057
And Tails is running from USB drive "to_upgrade" 0.418
And the boot device has safe access rights 4.073
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.670
After features/support/hooks.rb:330 1.454
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:44.783
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 14.261
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
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.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.078
And Tor is ready 21.088
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.916
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.390
Given I shutdown Tails and wait for the computer to power off 11.925
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.832
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.354
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.391
# 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.297
When the network is plugged 0.101
And Tor is ready 19.961
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.905
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.142
Given I shutdown Tails and wait for the computer to power off 7.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.816
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.571
And the file system changes introduced in version 6.3~testoverlayfs are present 0.643
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.449
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.068
And Tor is ready 20.935
Then the Upgrader considers the system as up-to-date 11.144
# 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.718
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.364
After features/support/hooks.rb:330 1.334
After features/support/hooks.rb:100 0.060
Tags: @product @automatic_upgrade
41.019
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.038
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.863
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.106
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 18.433
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.127
After features/support/hooks.rb:330 2.619
After features/support/hooks.rb:100 0.000