Project Number Date
test_Tails_ISO_devel 3751 24 Mar 2025, 13:31

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 20:32.682 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.516
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.239
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 36.882
When I start Tails from USB drive "old" with network unplugged 1:27.025
Then the boot device has safe access rights 3.192
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.602
After features/support/hooks.rb:100 0.016
Tags: @product
2:9.203
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.276
And I start Tails from USB drive "old" with network unplugged and I login 1:26.394
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 30.701
And I take note of which tps features are available 1.840
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.732
After features/support/hooks.rb:330 0.185
After features/support/hooks.rb:100 0.011
Tags: @product
2:51.172
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.142
Then Tails is running from USB drive "old" 0.836
And all tps features are active 2.147
When I write some files expected to persist 1.927
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.488
And all persistent directories from the old Tails version have safe access rights 3.788
And I take note of which tps features are available 0.511
And I shutdown Tails and wait for the computer to power off 4.509
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.323
After features/support/hooks.rb:330 0.120
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.507
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 11.913
And I log in to a new session 20.611
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.424
And I plug USB drive "to_upgrade" 2.485
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.718
Then the running Tails is installed on USB drive "to_upgrade" 21.854
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:330 2.384
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.354
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.824
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.955
Then all tps features from the old Tails version are active 2.600
And Tails is running from USB drive "to_upgrade" 0.408
And the boot device has safe access rights 3.786
And the expected persistent files created with the old Tails version are present in the filesystem 1.841
And all persistent directories from the old Tails version have safe access rights 2.937
After features/support/hooks.rb:330 2.062
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:34.842
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 52.322
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.459
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.525
When the network is plugged 0.078
And Tor is ready 23.136
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.963
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.916
Given I shutdown Tails and wait for the computer to power off 8.510
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.043
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.726
And the file system changes introduced in version 6.2~testoverlayfs are present 0.379
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.272
When the network is plugged 0.090
And Tor is ready 19.841
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.100
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.422
Given I shutdown Tails and wait for the computer to power off 4.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.885
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.511
And the file system changes introduced in version 6.3~testoverlayfs are present 0.599
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.081
And Tor is ready 19.752
Then the Upgrader considers the system as up-to-date 0.350
# 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.918
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.966
After features/support/hooks.rb:330 0.865
After features/support/hooks.rb:100 0.044
Tags: @product @automatic_upgrade
37.085
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 10.286
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.136
And Tor is ready 18.844
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.295
After features/support/hooks.rb:330 0.731
After features/support/hooks.rb:100 0.000