Project Number Date
test_Tails_ISO_stable 5744 27 Jun 2025, 10: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 26:25.897 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.531
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 41.646
When I start Tails from USB drive "old" with network unplugged 2:2.776
Then the boot device has safe access rights 6.794
And Tails is running from USB drive "old" 0.881
And there is no persistence partition on USB drive "old" 0.177
And process "udev-watchdog" is running 0.164
And udev-watchdog is monitoring the correct device 0.508
And I unplug USB drive "old" 0.249
After features/support/hooks.rb:330 4.725
After features/support/hooks.rb:100 0.011
Tags: @product
3:5.107
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 2:4.520
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 42.675
And I take note of which tps features are available 5.516
Then a Tails persistence partition exists on USB drive "old" 2.466
And I shutdown Tails and wait for the computer to power off 9.328
After features/support/hooks.rb:330 0.313
After features/support/hooks.rb:100 0.009
Tags: @product
4:15.823
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:14.234
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.659
When I write some files expected to persist 3.807
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.373
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 7.378
And I take note of which tps features are available 0.655
And I shutdown Tails and wait for the computer to power off 8.507
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 37.213
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.007
Tags: @product
3:16.551
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 without a persistent partition and stopped at Tails Greeter's login screen 13.090
And I log in to a new session 27.202
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.852
And I plug USB drive "to_upgrade" 2.953
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:54.067
Then the running Tails is installed on USB drive "to_upgrade" 36.776
And I unplug USB drive "to_upgrade" 0.246
And I unplug USB drive "__internal" 0.362
After features/support/hooks.rb:330 1.196
After features/support/hooks.rb:100 0.000
Tags: @product
3:4.286
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:46.947
Then all tps features from the old Tails version are active 3.754
And Tails is running from USB drive "to_upgrade" 1.538
And the boot device has safe access rights 7.651
And the expected persistent files created with the old Tails version are present in the filesystem 1.556
And all persistent directories from the old Tails version have safe access rights 2.643
After features/support/hooks.rb:330 2.024
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
8:56.935
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 16.972
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.653
When the network is plugged 0.135
And Tor is ready 23.597
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.810
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.622
Given I shutdown Tails and wait for the computer to power off 14.165
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:51.106
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 3.590
And the file system changes introduced in version 6.2~testoverlayfs are present 0.406
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.338
# 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.382
When the network is plugged 0.075
And Tor is ready 27.191
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.880
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.016
Given I shutdown Tails and wait for the computer to power off 6.795
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:43.703
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 7.196
And the file system changes introduced in version 6.3~testoverlayfs are present 1.334
And only the 6.3~testoverlayfs SquashFS delta is installed 0.169
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.514
When the network is plugged 0.100
And Tor is ready 22.346
Then the Upgrader considers the system as up-to-date 0.331
# 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 21.559
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.593
After features/support/hooks.rb:330 0.737
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
52.661
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 15.731
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
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.086
And Tor is ready 20.732
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 15.678
After features/support/hooks.rb:330 1.465
After features/support/hooks.rb:100 0.000