Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 32 01 Apr 2025, 21:34

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:48.095 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
1:54.818
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
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" 28.802
When I start Tails from USB drive "old" with network unplugged 1:20.744
Then the boot device has safe access rights 2.967
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 7.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.584
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:21.690
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 30.966
And I take note of which tps features are available 1.278
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.301
After features/support/hooks.rb:330 0.225
After features/support/hooks.rb:100 0.008
Tags: @product
2:49.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.700
Then Tails is running from USB drive "old" 0.355
And all tps features are active 1.953
When I write some files expected to persist 3.009
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 3.289
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 4.324
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.181
After features/support/hooks.rb:330 0.118
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.156
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 without a persistent partition and stopped at Tails Greeter's login screen 9.993
And I log in to a new session 19.884
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.707
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.105
Then the running Tails is installed on USB drive "to_upgrade" 25.568
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:330 0.963
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.657
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.163
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.156
Then all tps features from the old Tails version are active 1.626
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.204
And the expected persistent files created with the old Tails version are present in the filesystem 1.337
And all persistent directories from the old Tails version have safe access rights 2.806
After features/support/hooks.rb:330 0.979
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:29.583
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 11.431
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.068
And Tor is ready 19.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.657
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.096
Given I shutdown Tails and wait for the computer to power off 8.726
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.999
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.011
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.232
When the network is plugged 0.068
And Tor is ready 18.323
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.634
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.408
Given I shutdown Tails and wait for the computer to power off 4.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.493
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.915
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.074
And Tor is ready 20.025
Then the Upgrader considers the system as up-to-date 0.362
# 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.217
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.890
After features/support/hooks.rb:330 0.674
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.215
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.894
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 22.976
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.834
After features/support/hooks.rb:330 0.645
After features/support/hooks.rb:100 0.000