Project Number Date
test_Tails_ISO_stable 5694 02 Jun 2025, 16:00

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 21:27.239 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:20.481
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.283
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.095
And I write an old version of the Tails USB image to disk "old" 33.264
When I start Tails from USB drive "old" with network unplugged 1:40.612
Then the boot device has safe access rights 3.988
And Tails is running from USB drive "old" 0.484
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:330 7.071
After features/support/hooks.rb:100 0.010
Tags: @product
2:24.144
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login 1:38.392
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 33.537
And I take note of which tps features are available 2.079
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 8.758
After features/support/hooks.rb:330 0.210
After features/support/hooks.rb:100 0.010
Tags: @product
3:14.849
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.101
Then Tails is running from USB drive "old" 1.173
And all tps features are active 3.849
When I write some files expected to persist 2.755
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.763
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.899
And I take note of which tps features are available 0.430
And I shutdown Tails and wait for the computer to power off 5.515
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.764
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.007
Tags: @product
2:44.057
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 10.645
And I log in to a new session 20.511
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.200
And I plug USB drive "to_upgrade" 2.580
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.197
Then the running Tails is installed on USB drive "to_upgrade" 32.436
And I unplug USB drive "to_upgrade" 0.262
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:330 2.321
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.766
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.251
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.030
Then all tps features from the old Tails version are active 1.718
And Tails is running from USB drive "to_upgrade" 0.403
And the boot device has safe access rights 3.896
And the expected persistent files created with the old Tails version are present in the filesystem 1.600
And all persistent directories from the old Tails version have safe access rights 2.865
After features/support/hooks.rb:330 1.259
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:14.230
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 11.736
And no SquashFS delta is installed 0.343
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.074
And Tor is ready 26.603
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.201
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.568
Given I shutdown Tails and wait for the computer to power off 10.884
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.794
Then Tails is running version 6.2~testoverlayfs 0.799
And all tps features are active 2.715
And the file system changes introduced in version 6.2~testoverlayfs are present 0.405
And only the 6.2~testoverlayfs SquashFS delta is installed 0.112
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.385
# 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.335
When the network is plugged 1.126
And Tor is ready 21.585
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.546
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.243
Given I shutdown Tails and wait for the computer to power off 6.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.593
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.331
And the file system changes introduced in version 6.3~testoverlayfs are present 0.571
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.324
When the network is plugged 0.073
And Tor is ready 21.118
Then the Upgrader considers the system as up-to-date 0.338
# 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.129
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.899
After features/support/hooks.rb:330 0.769
After features/support/hooks.rb:100 0.057
Tags: @product @automatic_upgrade
1:2.708
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.564
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.570
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.087
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 49.574
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.719
After features/support/hooks.rb:330 0.884
After features/support/hooks.rb:100 0.000