Project Number Date
test_Tails_ISO_stable 5632 07 May 2025, 18:25

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:4.014 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:28.527
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.889
And I create a 7200 MiB disk named "old" 1.069
And I plug USB drive "old" 1.316
And I write an old version of the Tails USB image to disk "old" 39.102
When I start Tails from USB drive "old" with network unplugged 1:40.597
Then the boot device has safe access rights 3.286
And Tails is running from USB drive "old" 1.267
And there is no persistence partition on USB drive "old" 0.245
And process "udev-watchdog" is running 0.199
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:330 7.131
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.867
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login 1:40.931
Then Tails is running from USB drive "old" 0.494
And I create a persistent partition 36.230
And I take note of which tps features are available 2.805
Then a Tails persistence partition exists on USB drive "old" 0.997
And I shutdown Tails and wait for the computer to power off 10.166
After features/support/hooks.rb:330 0.248
After features/support/hooks.rb:100 0.009
Tags: @product
3:32.054
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:48.747
Then Tails is running from USB drive "old" 0.412
And all tps features are active 2.925
When I write some files expected to persist 2.341
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.282
And all persistence configuration files have safe access rights 0.493
And all persistent directories from the old Tails version have safe access rights 2.972
And I take note of which tps features are available 0.703
And I shutdown Tails and wait for the computer to power off 6.854
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.089
After features/support/hooks.rb:330 0.122
After features/support/hooks.rb:100 0.008
Tags: @product
2:45.603
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 without a persistent partition and stopped at Tails Greeter's login screen 13.973
And I log in to a new session 20.434
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.751
And I plug USB drive "to_upgrade" 2.442
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.449
Then the running Tails is installed on USB drive "to_upgrade" 28.101
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:330 3.476
After features/support/hooks.rb:100 0.000
Tags: @product
2:36.393
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.259
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.651
Then all tps features from the old Tails version are active 2.098
And Tails is running from USB drive "to_upgrade" 0.403
And the boot device has safe access rights 3.710
And the expected persistent files created with the old Tails version are present in the filesystem 1.566
And all persistent directories from the old Tails version have safe access rights 2.706
After features/support/hooks.rb:330 1.341
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:18.348
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 36.311
And no SquashFS delta is installed 0.194
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.531
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.435
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.483
When the network is plugged 0.117
And Tor is ready 23.866
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.873
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.426
Given I shutdown Tails and wait for the computer to power off 11.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:32.538
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 9.358
And the file system changes introduced in version 6.2~testoverlayfs are present 0.358
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.484
When the network is plugged 0.575
And Tor is ready 15.724
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.316
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.418
Given I shutdown Tails and wait for the computer to power off 9.037
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.718
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.526
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.348
When the network is plugged 0.082
And Tor is ready 48.444
Then the Upgrader considers the system as up-to-date 0.392
# 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 17.893
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.061
After features/support/hooks.rb:330 1.332
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
51.220
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 16.622
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.491
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
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.324
And Tor is ready 25.715
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.850
After features/support/hooks.rb:330 0.867
After features/support/hooks.rb:100 0.000