Project Number Date
test_Tails_ISO_devel 4047 01 Nov 2025, 12:15

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 16:57.668 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:2.403
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 34.862
When I start Tails from USB drive "old" with network unplugged 1:22.252
Then the boot device has safe access rights 3.152
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.246
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:331 3.890
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.124
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:32.396
Then Tails is running from USB drive "old" 0.691
And I create a persistent partition 30.627
And I take note of which tps features are available 8.048
Then a Tails persistence partition exists on USB drive "old" 0.866
And I shutdown Tails and wait for the computer to power off 7.279
After features/support/hooks.rb:331 0.478
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.354
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:42.049
Then Tails is running from USB drive "old" 0.317
And all tps features are active 2.948
When I write some files expected to persist 2.148
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.303
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.530
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 7.756
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.262
After features/support/hooks.rb:331 0.232
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.585
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 without a persistent partition and stopped at Tails Greeter's login screen 13.746
And I log in to a new session 19.072
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.467
And I plug USB drive "to_upgrade" 2.334
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.260
Then the running Tails is installed on USB drive "to_upgrade" 23.278
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:331 3.980
After features/support/hooks.rb:100 0.000
Tags: @product
1:55.518
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.714
Then all tps features from the old Tails version are active 2.056
And Tails is running from USB drive "to_upgrade" 0.392
And the boot device has safe access rights 3.402
And the expected persistent files created with the old Tails version are present in the filesystem 1.519
And all persistent directories from the old Tails version have safe access rights 2.258
After features/support/hooks.rb:331 0.884
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:16.567
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.902
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.064
And Tor is ready 14.976
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.952
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.743
Given I shutdown Tails and wait for the computer to power off 12.246
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.960
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.445
And the file system changes introduced in version 6.2~testoverlayfs are present 0.254
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.192
# 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.253
When the network is plugged 0.060
And Tor is ready 11.774
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.249
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.433
Given I shutdown Tails and wait for the computer to power off 5.176
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.417
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 2.481
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.054
And Tor is ready 13.080
Then the Upgrader considers the system as up-to-date 0.253
# 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 5.960
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.454
After features/support/hooks.rb:331 1.146
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
25.114
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.853
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 13.024
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.627
After features/support/hooks.rb:331 1.049
After features/support/hooks.rb:100 0.000