Project Number Date
test_Tails_ISO_devel 3784 16 Apr 2025, 13:52

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:38.330 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.970
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.313
When I start Tails from USB drive "old" with network unplugged 1:33.345
Then the boot device has safe access rights 3.035
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:330 3.493
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.468
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:26.679
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 32.374
And I take note of which tps features are available 2.566
Then a Tails persistence partition exists on USB drive "old" 0.887
And I shutdown Tails and wait for the computer to power off 8.425
After features/support/hooks.rb:330 0.234
After features/support/hooks.rb:100 0.022
Tags: @product
2:55.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.358
Then Tails is running from USB drive "old" 0.833
And all tps features are active 2.025
When I write some files expected to persist 2.089
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.327
And all persistence configuration files have safe access rights 0.810
And all persistent directories from the old Tails version have safe access rights 2.639
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 6.346
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.337
After features/support/hooks.rb:330 0.109
After features/support/hooks.rb:100 0.011
Tags: @product
2:37.018
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 without a persistent partition and stopped at Tails Greeter's login screen 11.884
And I log in to a new session 20.389
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.643
And I plug USB drive "to_upgrade" 2.382
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.349
Then the running Tails is installed on USB drive "to_upgrade" 25.911
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:330 0.813
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.811
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.245
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.025
Then all tps features from the old Tails version are active 2.081
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.617
And the expected persistent files created with the old Tails version are present in the filesystem 1.696
And all persistent directories from the old Tails version have safe access rights 2.811
After features/support/hooks.rb:330 0.923
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:49.805
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 11.854
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.524
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.080
And Tor is ready 22.766
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.905
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.709
Given I shutdown Tails and wait for the computer to power off 8.838
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.515
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.221
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.333
When the network is plugged 0.075
And Tor is ready 15.639
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.315
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.974
Given I shutdown Tails and wait for the computer to power off 1:1.503
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.045
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.999
And the file system changes introduced in version 6.3~testoverlayfs are present 0.564
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.396
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.328
When the network is plugged 0.076
And Tor is ready 19.475
Then the Upgrader considers the system as up-to-date 0.351
# 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 16.938
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.596
After features/support/hooks.rb:330 0.754
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
34.820
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 10.003
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.510
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 17.424
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.690
After features/support/hooks.rb:330 0.956
After features/support/hooks.rb:100 0.000