Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 1 04 Mar 2025, 15: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 19:42.109 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:21.662
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.532
And I create a 7200 MiB disk named "old" 0.374
And I plug USB drive "old" 1.152
And I write an old version of the Tails USB image to disk "old" 47.838
When I start Tails from USB drive "old" with network unplugged 1:27.561
Then the boot device has safe access rights 3.176
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 3.897
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.967
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login 1:35.682
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 30.903
And I take note of which tps features are available 1.514
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.454
After features/support/hooks.rb:330 0.241
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.687
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.038
Then Tails is running from USB drive "old" 0.452
And all tps features are active 2.115
When I write some files expected to persist 2.180
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.100
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.562
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 6.571
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.503
After features/support/hooks.rb:330 0.112
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.990
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.250
And I log in to a new session 19.215
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.843
And I plug USB drive "to_upgrade" 2.437
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.539
Then the running Tails is installed on USB drive "to_upgrade" 21.275
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:330 2.079
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.665
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.766
Then all tps features from the old Tails version are active 1.714
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.678
And the expected persistent files created with the old Tails version are present in the filesystem 1.420
And all persistent directories from the old Tails version have safe access rights 2.556
After features/support/hooks.rb:330 1.216
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:45.448
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 12.081
And no SquashFS delta is installed 0.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.638
When the network is plugged 0.075
And Tor is ready 20.795
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.606
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.958
Given I shutdown Tails and wait for the computer to power off 8.954
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.099
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.001
And the file system changes introduced in version 6.2~testoverlayfs are present 0.402
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.475
# 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.344
When the network is plugged 0.088
And Tor is ready 45.489
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.610
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.087
Given I shutdown Tails and wait for the computer to power off 4.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.130
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.061
And the file system changes introduced in version 6.3~testoverlayfs are present 0.594
And only the 6.3~testoverlayfs SquashFS delta is installed 0.112
# 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.495
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.423
When the network is plugged 0.072
And Tor is ready 17.746
Then the Upgrader considers the system as up-to-date 0.303
# 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.267
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.232
After features/support/hooks.rb:330 0.737
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.688
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 9.758
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.109
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 20.970
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.266
After features/support/hooks.rb:330 0.685
After features/support/hooks.rb:100 0.000