Project Number Date
test_Tails_ISO_stable 5487 03 Mar 2025, 16:20

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:7.522 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:25.491
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 31.672
When I start Tails from USB drive "old" with network unplugged 1:47.726
Then the boot device has safe access rights 3.563
And Tails is running from USB drive "old" 0.399
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.258
After features/support/hooks.rb:330 3.722
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.161
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login 1:28.843
Then Tails is running from USB drive "old" 0.381
And I create a persistent partition 35.038
And I take note of which tps features are available 1.575
Then a Tails persistence partition exists on USB drive "old" 0.986
And I shutdown Tails and wait for the computer to power off 9.096
After features/support/hooks.rb:330 0.326
After features/support/hooks.rb:100 0.012
Tags: @product
2:58.446
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.779
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.924
Then Tails is running from USB drive "old" 1.066
And all tps features are active 2.087
When I write some files expected to persist 1.823
# 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.476
And all persistent directories from the old Tails version have safe access rights 3.993
And I take note of which tps features are available 0.602
And I shutdown Tails and wait for the computer to power off 4.345
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.100
After features/support/hooks.rb:330 0.117
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.718
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.695
And I log in to a new session 21.864
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.872
And I plug USB drive "to_upgrade" 2.565
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.687
Then the running Tails is installed on USB drive "to_upgrade" 23.536
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.258
After features/support/hooks.rb:330 2.647
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.373
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.237
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.548
Then all tps features from the old Tails version are active 1.794
And Tails is running from USB drive "to_upgrade" 0.387
And the boot device has safe access rights 3.248
And the expected persistent files created with the old Tails version are present in the filesystem 1.545
And all persistent directories from the old Tails version have safe access rights 2.612
After features/support/hooks.rb:330 1.633
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:42.475
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.666
And no SquashFS delta is installed 0.607
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.468
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.566
When the network is plugged 0.077
And Tor is ready 24.732
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.018
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.302
Given I shutdown Tails and wait for the computer to power off 13.621
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.284
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 3.687
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.432
# 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.286
When the network is plugged 0.077
And Tor is ready 20.585
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.979
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.482
Given I shutdown Tails and wait for the computer to power off 4.389
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.896
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.183
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.082
And Tor is ready 19.991
Then the Upgrader considers the system as up-to-date 0.325
# 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.652
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.050
After features/support/hooks.rb:330 0.775
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.854
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 9.887
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
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.076
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 19.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.521
After features/support/hooks.rb:330 1.542
After features/support/hooks.rb:100 0.000