Project Number Date
test_Tails_ISO_stable 5739 25 Jun 2025, 17:57

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 22:7.370 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:54.223
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.240
When I start Tails from USB drive "old" with network unplugged 2:18.499
Then the boot device has safe access rights 3.859
And Tails is running from USB drive "old" 0.520
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.260
After features/support/hooks.rb:330 3.807
After features/support/hooks.rb:100 0.012
Tags: @product
2:24.041
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.289
And I start Tails from USB drive "old" with network unplugged and I login 1:36.709
Then Tails is running from USB drive "old" 0.534
And I create a persistent partition 34.560
And I take note of which tps features are available 2.400
Then a Tails persistence partition exists on USB drive "old" 0.921
And I shutdown Tails and wait for the computer to power off 8.624
After features/support/hooks.rb:330 0.171
After features/support/hooks.rb:100 0.010
Tags: @product
3:18.590
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:40.048
Then Tails is running from USB drive "old" 0.353
And all tps features are active 2.037
When I write some files expected to persist 2.136
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.436
And I take note of which tps features are available 0.495
And I shutdown Tails and wait for the computer to power off 4.505
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.726
After features/support/hooks.rb:330 0.150
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.644
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.625
And I log in to a new session 19.758
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.730
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.232
Then the running Tails is installed on USB drive "to_upgrade" 24.482
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 3.297
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.675
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.232
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.767
Then all tps features from the old Tails version are active 1.580
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.478
And the expected persistent files created with the old Tails version are present in the filesystem 1.587
And all persistent directories from the old Tails version have safe access rights 2.685
After features/support/hooks.rb:330 1.716
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
7:58.934
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 10.776
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.465
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.464
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.572
When the network is plugged 0.066
And Tor is ready 23.787
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.931
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.920
Given I shutdown Tails and wait for the computer to power off 1:27.232
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.169
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.201
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.274
When the network is plugged 0.088
And Tor is ready 18.476
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.892
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.171
Given I shutdown Tails and wait for the computer to power off 6.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.412
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.122
And the file system changes introduced in version 6.3~testoverlayfs are present 0.558
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.368
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.064
And Tor is ready 18.852
Then the Upgrader considers the system as up-to-date 0.381
# 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 15.400
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.611
After features/support/hooks.rb:330 0.686
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
37.259
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 with a persistent partition enabled and logged in 9.782
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.910
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.093
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 19.306
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.021
After features/support/hooks.rb:330 0.712
After features/support/hooks.rb:100 0.000