Project Number Date
test_Tails_ISO_stable 5709 10 Jun 2025, 20:56

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 20:42.755 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:11.188
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.406
When I start Tails from USB drive "old" with network unplugged 1:34.188
Then the boot device has safe access rights 3.209
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.258
After features/support/hooks.rb:330 7.214
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.498
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:28.314
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 35.719
And I take note of which tps features are available 1.661
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 8.472
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.357
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.890
Then Tails is running from USB drive "old" 1.149
And all tps features are active 2.205
When I write some files expected to persist 2.787
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.771
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.684
And I take note of which tps features are available 0.419
And I shutdown Tails and wait for the computer to power off 6.486
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.365
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.012
Tags: @product
2:37.968
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.960
And I log in to a new session 18.208
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.952
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.936
Then the running Tails is installed on USB drive "to_upgrade" 27.037
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:330 8.227
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.754
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 "to_upgrade" with network unplugged and I login with persistence enabled 2:7.795
Then all tps features from the old Tails version are active 1.675
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.704
And the expected persistent files created with the old Tails version are present in the filesystem 1.536
And all persistent directories from the old Tails version have safe access rights 2.460
After features/support/hooks.rb:330 1.468
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:1.649
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 13.508
And no SquashFS delta is installed 0.217
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.338
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.233
And Tor is ready 21.459
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.542
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.498
Given I shutdown Tails and wait for the computer to power off 10.845
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.408
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.156
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.287
# 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.384
When the network is plugged 0.074
And Tor is ready 21.559
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.463
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.792
Given I shutdown Tails and wait for the computer to power off 6.443
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.130
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.025
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.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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.054
And Tor is ready 20.103
Then the Upgrader considers the system as up-to-date 0.326
# 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.825
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.484
After features/support/hooks.rb:330 0.705
After features/support/hooks.rb:100 0.061
Tags: @product @automatic_upgrade
1:16.338
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 25.391
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 48.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.629
After features/support/hooks.rb:330 0.646
After features/support/hooks.rb:100 0.000