Project Number Date
test_Tails_ISO_stable 5653 17 May 2025, 12:44

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 19:52.123 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:8.643
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.820
When I start Tails from USB drive "old" with network unplugged 1:30.508
Then the boot device has safe access rights 3.033
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.128
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:330 3.725
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.211
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:22.525
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 31.345
And I take note of which tps features are available 1.643
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.394
After features/support/hooks.rb:330 0.173
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.013
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:15.173
Then Tails is running from USB drive "old" 0.427
And all tps features are active 2.098
When I write some files expected to persist 1.829
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.522
And I take note of which tps features are available 0.390
And I shutdown Tails and wait for the computer to power off 4.426
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.331
After features/support/hooks.rb:330 0.116
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.543
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 10.126
And I log in to a new session 18.672
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.626
And I plug USB drive "to_upgrade" 2.557
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.360
Then the running Tails is installed on USB drive "to_upgrade" 25.803
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:330 1.196
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.459
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.336
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.803
Then all tps features from the old Tails version are active 1.648
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.252
And the expected persistent files created with the old Tails version are present in the filesystem 1.624
And all persistent directories from the old Tails version have safe access rights 2.462
After features/support/hooks.rb:330 1.523
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:20.769
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 11.502
And no SquashFS delta is installed 0.358
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.475
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.075
And Tor is ready 22.729
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.327
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.915
Given I shutdown Tails and wait for the computer to power off 9.035
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.133
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.245
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.290
# 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.317
When the network is plugged 0.088
And Tor is ready 16.889
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.474
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.497
Given I shutdown Tails and wait for the computer to power off 58.529
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.344
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.859
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.268
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.349
When the network is plugged 0.068
And Tor is ready 19.321
Then the Upgrader considers the system as up-to-date 0.358
# 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.405
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.047
After features/support/hooks.rb:330 0.743
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.481
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 9.670
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.609
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 21.973
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.949
After features/support/hooks.rb:330 0.989
After features/support/hooks.rb:100 0.000