Project Number Date
test_Tails_ISO_stable 5973 27 Nov 2025, 15:47

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 17:23.634 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:9.506
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.124
And I plug USB drive "old" 1.097
And I write an old version of the Tails USB image to disk "old" 33.354
When I start Tails from USB drive "old" with network unplugged 1:31.076
Then the boot device has safe access rights 2.784
And Tails is running from USB drive "old" 0.262
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:331 4.195
After features/support/hooks.rb:100 0.013
Tags: @product
2:17.509
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:35.152
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 31.482
And I take note of which tps features are available 1.347
Then a Tails persistence partition exists on USB drive "old" 1.030
And I shutdown Tails and wait for the computer to power off 7.985
After features/support/hooks.rb:331 0.252
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.231
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:45.063
Then Tails is running from USB drive "old" 0.365
And all tps features are active 2.306
When I write some files expected to persist 1.954
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.475
And all persistent directories from the old Tails version have safe access rights 2.488
And I take note of which tps features are available 0.547
And I shutdown Tails and wait for the computer to power off 7.590
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.012
After features/support/hooks.rb:331 0.348
After features/support/hooks.rb:100 0.016
Tags: @product
3:3.328
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.345
And I log in to a new session 19.553
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.335
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:2.605
Then the running Tails is installed on USB drive "to_upgrade" 23.727
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:331 4.360
After features/support/hooks.rb:100 0.000
Tags: @product
1:52.369
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:42.532
Then all tps features from the old Tails version are active 1.994
And Tails is running from USB drive "to_upgrade" 0.549
And the boot device has safe access rights 3.427
And the expected persistent files created with the old Tails version are present in the filesystem 1.271
And all persistent directories from the old Tails version have safe access rights 2.431
After features/support/hooks.rb:331 0.624
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:15.617
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 14.691
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
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.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.055
And Tor is ready 15.589
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.096
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.595
Given I shutdown Tails and wait for the computer to power off 11.962
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.033
Then Tails is running version 6.2~testoverlayfs 0.048
And all tps features are active 2.697
And the file system changes introduced in version 6.2~testoverlayfs are present 0.448
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.205
# 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.249
When the network is plugged 0.060
And Tor is ready 12.440
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.646
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.212
Given I shutdown Tails and wait for the computer to power off 3.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.145
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.314
And the file system changes introduced in version 6.3~testoverlayfs are present 0.460
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.191
And Tor is ready 12.886
Then the Upgrader considers the system as up-to-date 0.224
# 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 6.518
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.531
After features/support/hooks.rb:331 0.787
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
25.072
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.641
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 12.136
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.793
After features/support/hooks.rb:331 0.843
After features/support/hooks.rb:100 0.000