Project Number Date
test_Tails_ISO_devel 4082 21 Nov 2025, 12:40

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:12.815 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:51.009
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 30.925
When I start Tails from USB drive "old" with network unplugged 1:15.211
Then the boot device has safe access rights 2.663
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.269
After features/support/hooks.rb:331 3.751
After features/support/hooks.rb:100 0.009
Tags: @product
2:1.604
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:24.845
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 26.548
And I take note of which tps features are available 1.231
Then a Tails persistence partition exists on USB drive "old" 0.728
And I shutdown Tails and wait for the computer to power off 7.732
After features/support/hooks.rb:331 0.560
After features/support/hooks.rb:100 0.012
Tags: @product
2:6.296
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.261
Then Tails is running from USB drive "old" 0.277
And all tps features are active 1.884
When I write some files expected to persist 1.588
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.313
And all persistent directories from the old Tails version have safe access rights 2.616
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 7.498
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.044
After features/support/hooks.rb:331 0.666
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.740
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.180
And I log in to a new session 15.739
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.572
And I plug USB drive "to_upgrade" 2.390
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.809
Then the running Tails is installed on USB drive "to_upgrade" 20.032
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 1.794
After features/support/hooks.rb:331 3.627
After features/support/hooks.rb:100 0.000
Tags: @product
1:46.252
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.581
Then all tps features from the old Tails version are active 1.787
And Tails is running from USB drive "to_upgrade" 0.243
And the boot device has safe access rights 2.887
And the expected persistent files created with the old Tails version are present in the filesystem 1.347
And all persistent directories from the old Tails version have safe access rights 2.243
After features/support/hooks.rb:331 0.588
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:54.653
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 13.227
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.060
And Tor is ready 13.626
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.859
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.966
Given I shutdown Tails and wait for the computer to power off 11.351
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.885
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.007
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.247
When the network is plugged 0.064
And Tor is ready 11.781
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.743
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.169
Given I shutdown Tails and wait for the computer to power off 3.075
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.013
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.020
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.176
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.247
When the network is plugged 0.097
And Tor is ready 10.989
Then the Upgrader considers the system as up-to-date 0.243
# 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.231
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.495
After features/support/hooks.rb:331 0.972
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
53.258
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 11.994
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
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.051
And Tor is ready 40.198
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.588
After features/support/hooks.rb:331 1.207
After features/support/hooks.rb:100 0.000