Project Number Date
test_Tails_ISO_devel 4121 14 Dec 2025, 12:33

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 15:15.070 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
1:50.755
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.103
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 31.795
When I start Tails from USB drive "old" with network unplugged 1:13.219
Then the boot device has safe access rights 3.232
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.124
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.353
After features/support/hooks.rb:331 3.845
After features/support/hooks.rb:100 0.092
Tags: @product
1:54.715
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.081
Given a computer 0.489
And I start Tails from USB drive "old" with network unplugged and I login 1:7.875
Then Tails is running from USB drive "old" 0.728
And I create a persistent partition 31.640
And I take note of which tps features are available 5.473
Then a Tails persistence partition exists on USB drive "old" 0.813
And I shutdown Tails and wait for the computer to power off 7.695
After features/support/hooks.rb:331 0.546
After features/support/hooks.rb:100 0.010
Tags: @product
2:2.405
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:27.676
Then Tails is running from USB drive "old" 0.872
And all tps features are active 1.898
When I write some files expected to persist 1.538
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 2.350
And I take note of which tps features are available 0.465
And I shutdown Tails and wait for the computer to power off 7.599
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.255
After features/support/hooks.rb:331 0.631
After features/support/hooks.rb:100 0.010
Tags: @product
2:49.997
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.966
And I log in to a new session 17.583
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.648
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.490
Then the running Tails is installed on USB drive "to_upgrade" 25.431
And I unplug USB drive "to_upgrade" 0.572
And I unplug USB drive "__internal" 0.810
After features/support/hooks.rb:331 4.398
After features/support/hooks.rb:100 0.000
Tags: @product
1:33.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:23.576
Then all tps features from the old Tails version are active 1.516
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 4.376
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.379
After features/support/hooks.rb:331 0.871
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:36.261
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 12.761
And no SquashFS delta is installed 0.142
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.182
And Tor is ready 15.654
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.950
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.396
Given I shutdown Tails and wait for the computer to power off 13.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.518
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.132
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.277
When the network is plugged 0.055
And Tor is ready 12.472
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.785
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.492
Given I shutdown Tails and wait for the computer to power off 7.668
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.909
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.337
And the file system changes introduced in version 6.3~testoverlayfs are present 0.586
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.180
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.079
And Tor is ready 12.053
Then the Upgrader considers the system as up-to-date 0.174
# 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 7.339
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.520
After features/support/hooks.rb:331 1.032
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
27.154
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 12.372
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 12.571
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.737
After features/support/hooks.rb:331 0.714
After features/support/hooks.rb:100 0.000