Project Number Date
test_Tails_ISO_stable 5747 28 Jun 2025, 12:48

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:4.329 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:3.330
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.949
When I start Tails from USB drive "old" with network unplugged 1:27.721
Then the boot device has safe access rights 3.208
And Tails is running from USB drive "old" 0.409
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.372
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:330 7.025
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.280
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:28.759
Then Tails is running from USB drive "old" 0.407
And I create a persistent partition 31.695
And I take note of which tps features are available 1.685
Then a Tails persistence partition exists on USB drive "old" 0.768
And I shutdown Tails and wait for the computer to power off 8.795
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.648
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 with persistence enabled 2:18.127
Then Tails is running from USB drive "old" 0.472
And all tps features are active 2.180
When I write some files expected to persist 1.730
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 2.340
And I take note of which tps features are available 0.384
And I shutdown Tails and wait for the computer to power off 6.332
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.233
After features/support/hooks.rb:330 0.230
After features/support/hooks.rb:100 0.024
Tags: @product
2:38.796
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 9.869
And I log in to a new session 19.557
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.424
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.566
Then the running Tails is installed on USB drive "to_upgrade" 27.412
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.247
After features/support/hooks.rb:330 0.809
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.421
Then all tps features from the old Tails version are active 1.546
And Tails is running from USB drive "to_upgrade" 0.461
And the boot device has safe access rights 3.134
And the expected persistent files created with the old Tails version are present in the filesystem 1.433
And all persistent directories from the old Tails version have safe access rights 2.417
After features/support/hooks.rb:330 0.601
After features/support/hooks.rb:100 0.009
7:14.233
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 12.449
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.458
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.061
And Tor is ready 24.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.526
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.320
Given I shutdown Tails and wait for the computer to power off 10.704
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.310
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.173
And the file system changes introduced in version 6.2~testoverlayfs are present 0.352
And only the 6.2~testoverlayfs SquashFS delta is installed 0.128
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.637
# 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.267
When the network is plugged 0.071
And Tor is ready 19.454
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.990
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.922
Given I shutdown Tails and wait for the computer to power off 4.785
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.857
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.762
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.378
When the network is plugged 0.062
And Tor is ready 46.739
Then the Upgrader considers the system as up-to-date 0.389
# 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.317
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.689
After features/support/hooks.rb:330 0.723
After features/support/hooks.rb:100 0.019
40.441
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.442
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 21.327
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.068
After features/support/hooks.rb:330 0.727
After features/support/hooks.rb:100 0.000