Project Number Date
test_Tails_ISO_devel 4053 05 Nov 2025, 09:13

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:47.924 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:59.125
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 25.709
When I start Tails from USB drive "old" with network unplugged 1:28.531
Then the boot device has safe access rights 2.737
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.252
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:331 3.621
After features/support/hooks.rb:100 0.011
Tags: @product
2:2.791
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:23.976
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 28.673
And I take note of which tps features are available 1.340
Then a Tails persistence partition exists on USB drive "old" 0.709
And I shutdown Tails and wait for the computer to power off 7.569
After features/support/hooks.rb:331 0.194
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.409
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.260
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:34.675
Then Tails is running from USB drive "old" 0.304
And all tps features are active 2.109
When I write some files expected to persist 1.558
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.518
And all persistent directories from the old Tails version have safe access rights 2.504
And I take note of which tps features are available 0.632
And I shutdown Tails and wait for the computer to power off 7.816
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.774
After features/support/hooks.rb:331 0.548
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.116
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 12.012
And I log in to a new session 16.561
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.677
And I plug USB drive "to_upgrade" 2.791
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.319
Then the running Tails is installed on USB drive "to_upgrade" 20.314
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:331 4.392
After features/support/hooks.rb:100 0.000
Tags: @product
1:45.297
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:36.385
Then all tps features from the old Tails version are active 1.560
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.219
And the expected persistent files created with the old Tails version are present in the filesystem 1.346
And all persistent directories from the old Tails version have safe access rights 2.230
After features/support/hooks.rb:331 1.193
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:56.497
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 11.426
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.084
And Tor is ready 15.235
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.749
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.015
Given I shutdown Tails and wait for the computer to power off 11.200
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.441
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.484
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.229
When the network is plugged 0.074
And Tor is ready 11.764
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.737
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.710
Given I shutdown Tails and wait for the computer to power off 3.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.615
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.484
And the file system changes introduced in version 6.3~testoverlayfs are present 0.436
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.166
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.061
And Tor is ready 12.723
Then the Upgrader considers the system as up-to-date 0.228
# 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.842
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.450
After features/support/hooks.rb:331 1.153
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
23.686
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 10.294
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 11.251
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.682
After features/support/hooks.rb:331 0.676
After features/support/hooks.rb:100 0.000