Project Number Date
test_Tails_ISO_stable 5477 22 Feb 2025, 12:49

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:46.578 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:6.220
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 32.694
When I start Tails from USB drive "old" with network unplugged 1:28.362
Then the boot device has safe access rights 2.886
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 10.328
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.313
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:27.268
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 32.731
And I take note of which tps features are available 1.489
Then a Tails persistence partition exists on USB drive "old" 0.900
And I shutdown Tails and wait for the computer to power off 8.347
After features/support/hooks.rb:330 0.268
After features/support/hooks.rb:100 0.015
Tags: @product
3:3.354
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.555
Then Tails is running from USB drive "old" 0.401
And all tps features are active 2.635
When I write some files expected to persist 2.155
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 2.525
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 4.323
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.435
After features/support/hooks.rb:330 0.116
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.424
And I log in to a new session 18.623
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.674
And I plug USB drive "to_upgrade" 2.794
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.412
Then the running Tails is installed on USB drive "to_upgrade" 24.378
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 2.196
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.111
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.765
Then all tps features from the old Tails version are active 1.628
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.562
And the expected persistent files created with the old Tails version are present in the filesystem 1.354
And all persistent directories from the old Tails version have safe access rights 2.281
After features/support/hooks.rb:330 1.130
After features/support/hooks.rb:100 0.009
7:59.305
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.644
And no SquashFS delta is installed 0.473
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.083
And Tor is ready 23.880
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.767
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.942
Given I shutdown Tails and wait for the computer to power off 1:30.709
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.480
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.521
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# 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.334
When the network is plugged 0.063
And Tor is ready 19.615
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.176
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.526
Given I shutdown Tails and wait for the computer to power off 4.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.817
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.171
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.066
And Tor is ready 19.802
Then the Upgrader considers the system as up-to-date 0.301
# 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.312
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.993
After features/support/hooks.rb:330 0.793
After features/support/hooks.rb:100 0.018
39.510
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.792
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.485
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 21.322
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.684
After features/support/hooks.rb:330 0.740
After features/support/hooks.rb:100 0.000