Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 4 07 Mar 2025, 07:07

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 18:57.161 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:3.114
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.034
When I start Tails from USB drive "old" with network unplugged 1:28.793
Then the boot device has safe access rights 3.028
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:330 6.749
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.738
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:20.974
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 31.533
And I take note of which tps features are available 1.545
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 8.365
After features/support/hooks.rb:330 0.201
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.354
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.839
Then Tails is running from USB drive "old" 0.316
And all tps features are active 1.872
When I write some files expected to persist 1.666
# 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.465
And all persistent directories from the old Tails version have safe access rights 2.805
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 4.335
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.186
After features/support/hooks.rb:330 0.109
After features/support/hooks.rb:100 0.007
Tags: @product
2:28.999
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.502
And I log in to a new session 18.305
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.758
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.498
Then the running Tails is installed on USB drive "to_upgrade" 21.115
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 1.876
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.096
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.731
Then all tps features from the old Tails version are active 1.573
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.032
And the expected persistent files created with the old Tails version are present in the filesystem 1.732
And all persistent directories from the old Tails version have safe access rights 2.499
After features/support/hooks.rb:330 0.715
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:46.640
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 12.130
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.529
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.118
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.074
And Tor is ready 49.268
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.651
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.627
Given I shutdown Tails and wait for the computer to power off 8.673
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.896
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.964
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.355
# 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.290
When the network is plugged 0.069
And Tor is ready 19.940
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.328
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.677
Given I shutdown Tails and wait for the computer to power off 4.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.191
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.029
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.278
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.071
And Tor is ready 18.064
Then the Upgrader considers the system as up-to-date 0.319
# 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.789
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.871
After features/support/hooks.rb:330 0.736
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.216
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.722
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.604
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 19.569
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.072
After features/support/hooks.rb:330 0.924
After features/support/hooks.rb:100 0.000