Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 8 12 Mar 2025, 09:11

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 21:0.643 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.276
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.086
And I write an old version of the Tails USB image to disk "old" 33.037
When I start Tails from USB drive "old" with network unplugged 1:42.337
Then the boot device has safe access rights 3.408
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.369
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:330 3.562
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.781
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:40.438
Then Tails is running from USB drive "old" 0.396
And I create a persistent partition 34.924
And I take note of which tps features are available 2.105
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 6.767
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.011
Tags: @product
3:26.345
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.266
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:44.886
Then Tails is running from USB drive "old" 0.358
And all tps features are active 2.232
When I write some files expected to persist 1.914
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.322
And all persistence configuration files have safe access rights 0.551
And all persistent directories from the old Tails version have safe access rights 3.152
And I take note of which tps features are available 0.411
And I shutdown Tails and wait for the computer to power off 6.744
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.504
After features/support/hooks.rb:330 0.139
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.208
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.879
And I log in to a new session 19.121
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.610
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.662
Then the running Tails is installed on USB drive "to_upgrade" 23.088
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 2.349
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.661
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.198
Then all tps features from the old Tails version are active 2.366
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.500
And the expected persistent files created with the old Tails version are present in the filesystem 1.505
And all persistent directories from the old Tails version have safe access rights 2.577
After features/support/hooks.rb:330 1.299
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:5.846
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 with a persistent partition enabled and logged in 24.945
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.443
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.607
When the network is plugged 0.083
And Tor is ready 24.832
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.718
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.853
Given I shutdown Tails and wait for the computer to power off 8.740
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.178
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.420
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.332
When the network is plugged 0.086
And Tor is ready 18.190
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.646
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.974
Given I shutdown Tails and wait for the computer to power off 6.722
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.647
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.330
And the file system changes introduced in version 6.3~testoverlayfs are present 0.597
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.369
When the network is plugged 0.067
And Tor is ready 18.482
Then the Upgrader considers the system as up-to-date 0.318
# 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.577
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.994
After features/support/hooks.rb:330 0.714
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.524
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.708
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.560
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the signing key used by the Upgrader is outdated 0.121
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 21.575
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.380
After features/support/hooks.rb:330 0.743
After features/support/hooks.rb:100 0.000