Project Number Date
test_Tails_ISO_stable 5656 19 May 2025, 09:53

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:30.773 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.898
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.259
And I create a 7200 MiB disk named "old" 0.101
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 34.177
When I start Tails from USB drive "old" with network unplugged 1:29.883
Then the boot device has safe access rights 3.265
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.271
After features/support/hooks.rb:330 3.731
After features/support/hooks.rb:100 0.011
Tags: @product
2:9.876
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:26.732
Then Tails is running from USB drive "old" 0.426
And I create a persistent partition 31.771
And I take note of which tps features are available 1.672
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 8.254
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.692
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.833
Then Tails is running from USB drive "old" 0.787
And all tps features are active 2.057
When I write some files expected to persist 1.660
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.714
And I take note of which tps features are available 0.409
And I shutdown Tails and wait for the computer to power off 6.419
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.931
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.595
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 without a persistent partition and stopped at Tails Greeter's login screen 10.362
And I log in to a new session 18.776
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.480
And I plug USB drive "to_upgrade" 2.390
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.150
Then the running Tails is installed on USB drive "to_upgrade" 24.026
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:330 3.248
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.861
Then all tps features from the old Tails version are active 1.806
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.897
And the expected persistent files created with the old Tails version are present in the filesystem 1.559
And all persistent directories from the old Tails version have safe access rights 2.616
After features/support/hooks.rb:330 0.708
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:49.710
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 12.549
And no SquashFS delta is installed 0.262
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.480
When the network is plugged 0.091
And Tor is ready 22.708
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.654
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.268
Given I shutdown Tails and wait for the computer to power off 10.817
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.961
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.256
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.342
When the network is plugged 0.073
And Tor is ready 20.810
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.500
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.898
Given I shutdown Tails and wait for the computer to power off 4.486
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.558
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.090
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.345
When the network is plugged 0.079
And Tor is ready 18.886
Then the Upgrader considers the system as up-to-date 0.308
# 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.486
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.365
After features/support/hooks.rb:330 0.825
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.625
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.140
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.048
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 21.574
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.653
After features/support/hooks.rb:330 0.683
After features/support/hooks.rb:100 0.000