Project Number Date
test_Tails_ISO_stable 5763 08 Jul 2025, 13:41

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 23:29.435 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:40.781
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given a computer 0.290
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 38.524
When I start Tails from USB drive "old" with network unplugged 1:55.987
Then the boot device has safe access rights 3.396
And Tails is running from USB drive "old" 0.405
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.164
And udev-watchdog is monitoring the correct device 0.637
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:330 11.005
After features/support/hooks.rb:100 0.013
Tags: @product
2:36.426
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 1:45.197
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 36.981
And I take note of which tps features are available 2.483
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 10.341
After features/support/hooks.rb:330 0.214
After features/support/hooks.rb:100 0.008
Tags: @product
3:38.623
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:47.516
Then Tails is running from USB drive "old" 1.504
And all tps features are active 2.250
When I write some files expected to persist 2.092
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.316
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 6.400
And I take note of which tps features are available 0.580
And I shutdown Tails and wait for the computer to power off 6.797
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 30.542
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.402
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 12.055
And I log in to a new session 28.138
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.675
And I plug USB drive "to_upgrade" 2.853
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.052
Then the running Tails is installed on USB drive "to_upgrade" 33.845
And I unplug USB drive "to_upgrade" 0.476
And I unplug USB drive "__internal" 0.305
After features/support/hooks.rb:330 3.544
After features/support/hooks.rb:100 0.000
Tags: @product
2:47.471
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:36.177
Then all tps features from the old Tails version are active 2.811
And Tails is running from USB drive "to_upgrade" 0.429
And the boot device has safe access rights 3.614
And the expected persistent files created with the old Tails version are present in the filesystem 1.461
And all persistent directories from the old Tails version have safe access rights 2.761
After features/support/hooks.rb:330 1.561
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:56.525
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 16.131
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.176
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.587
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.601
When the network is plugged 0.064
And Tor is ready 22.744
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.969
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.627
Given I shutdown Tails and wait for the computer to power off 11.535
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.520
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.490
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.301
When the network is plugged 0.069
And Tor is ready 22.112
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 11.338
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.743
Given I shutdown Tails and wait for the computer to power off 6.717
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.495
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 3.761
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.404
When the network is plugged 0.069
And Tor is ready 22.305
Then the Upgrader considers the system as up-to-date 0.333
# 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 18.355
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.917
After features/support/hooks.rb:330 0.773
After features/support/hooks.rb:100 0.050
Tags: @product @automatic_upgrade
47.205
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.809
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.749
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.127
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 22.238
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.156
After features/support/hooks.rb:330 1.366
After features/support/hooks.rb:100 0.000