Project Number Date
test_Tails_ISO_devel 3890 28 Jun 2025, 14:03

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 27:40.087 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:57.616
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 38.716
When I start Tails from USB drive "old" with network unplugged 2:7.845
Then the boot device has safe access rights 7.650
And Tails is running from USB drive "old" 0.491
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.536
And I unplug USB drive "old" 0.871
After features/support/hooks.rb:330 3.682
After features/support/hooks.rb:100 0.012
Tags: @product
3:3.425
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 2:3.607
Then Tails is running from USB drive "old" 0.486
And I create a persistent partition 44.222
And I take note of which tps features are available 4.081
Then a Tails persistence partition exists on USB drive "old" 2.127
And I shutdown Tails and wait for the computer to power off 8.684
After features/support/hooks.rb:330 0.239
After features/support/hooks.rb:100 0.013
Tags: @product
4:11.544
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:5.745
Then Tails is running from USB drive "old" 2.480
And all tps features are active 3.207
When I write some files expected to persist 2.180
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 3.298
And I take note of which tps features are available 0.788
And I shutdown Tails and wait for the computer to power off 10.503
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 42.389
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.021
Tags: @product
4:1.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 17.256
And I log in to a new session 31.112
And I clone USB drive "old" to a new USB drive "to_upgrade" 9.402
And I plug USB drive "to_upgrade" 5.764
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:10.848
Then the running Tails is installed on USB drive "to_upgrade" 46.727
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:330 3.932
After features/support/hooks.rb:100 0.000
Tags: @product
3:22.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.310
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:6.470
Then all tps features from the old Tails version are active 5.929
And Tails is running from USB drive "to_upgrade" 0.399
And the boot device has safe access rights 4.248
And the expected persistent files created with the old Tails version are present in the filesystem 1.562
And all persistent directories from the old Tails version have safe access rights 3.837
After features/support/hooks.rb:330 4.074
After features/support/hooks.rb:100 0.045
9:5.015
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.089
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.858
And no SquashFS delta is installed 0.199
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 2.690
When the network is plugged 1.648
And Tor is ready 28.381
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.508
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.823
Given I shutdown Tails and wait for the computer to power off 12.684
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:50.358
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 7.452
And the file system changes introduced in version 6.2~testoverlayfs are present 0.547
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.561
# 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.444
When the network is plugged 0.208
And Tor is ready 21.935
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.421
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.138
Given I shutdown Tails and wait for the computer to power off 8.028
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:47.752
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.294
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.370
When the network is plugged 0.068
And Tor is ready 24.804
Then the Upgrader considers the system as up-to-date 0.333
# 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 24.903
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.780
After features/support/hooks.rb:330 1.607
After features/support/hooks.rb:100 0.026
58.194
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.900
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.467
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.312
And the signing key used by the Upgrader is outdated 0.402
But a current signing key is available on our website 0.000
When the network is plugged 0.434
And Tor is ready 28.805
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.871
After features/support/hooks.rb:330 1.522
After features/support/hooks.rb:100 0.000