Project Number Date
test_Tails_ISO_devel 3782 14 Apr 2025, 13:35

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:43.248 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:23.329
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 33.877
When I start Tails from USB drive "old" with network unplugged 1:44.069
Then the boot device has safe access rights 3.069
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:330 3.528
After features/support/hooks.rb:100 0.092
Tags: @product
2:6.952
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login 1:24.087
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 31.440
And I take note of which tps features are available 1.786
Then a Tails persistence partition exists on USB drive "old" 0.743
And I shutdown Tails and wait for the computer to power off 8.240
After features/support/hooks.rb:330 0.197
After features/support/hooks.rb:100 0.013
Tags: @product
2:57.294
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.556
Then Tails is running from USB drive "old" 0.488
And all tps features are active 4.287
When I write some files expected to persist 1.820
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.283
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.454
And I take note of which tps features are available 0.539
And I shutdown Tails and wait for the computer to power off 4.294
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.947
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.018
Tags: @product
2:33.643
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.212
And I log in to a new session 18.302
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.595
And I plug USB drive "to_upgrade" 2.370
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.909
Then the running Tails is installed on USB drive "to_upgrade" 25.814
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 2.197
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.216
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.466
Then all tps features from the old Tails version are active 1.679
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.127
And the expected persistent files created with the old Tails version are present in the filesystem 1.489
And all persistent directories from the old Tails version have safe access rights 2.910
After features/support/hooks.rb:330 1.359
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
6:43.269
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.094
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.421
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.530
When the network is plugged 0.093
And Tor is ready 23.585
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.686
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.448
Given I shutdown Tails and wait for the computer to power off 8.656
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.901
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.437
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.284
When the network is plugged 0.072
And Tor is ready 17.668
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.450
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.912
Given I shutdown Tails and wait for the computer to power off 6.717
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.011
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.168
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.091
And Tor is ready 20.945
Then the Upgrader considers the system as up-to-date 0.317
# 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 14.962
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.474
After features/support/hooks.rb:330 0.819
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.541
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.220
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
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.343
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 17.960
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.554
After features/support/hooks.rb:330 1.946
After features/support/hooks.rb:100 0.000