Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 24 24 Mar 2025, 21:39

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:17.051 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.399
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 29.832
When I start Tails from USB drive "old" with network unplugged 1:19.356
Then the boot device has safe access rights 2.930
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 6.813
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.585
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:22.268
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 32.157
And I take note of which tps features are available 1.557
Then a Tails persistence partition exists on USB drive "old" 0.784
And I shutdown Tails and wait for the computer to power off 8.318
After features/support/hooks.rb:330 0.195
After features/support/hooks.rb:100 0.007
Tags: @product
2:43.142
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.734
Then Tails is running from USB drive "old" 0.744
And all tps features are active 1.978
When I write some files expected to persist 1.632
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.629
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 4.349
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.750
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.093
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 9.740
And I log in to a new session 18.842
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.570
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.928
Then the running Tails is installed on USB drive "to_upgrade" 20.121
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 2.326
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.085
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.040
Then all tps features from the old Tails version are active 1.707
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.065
And the expected persistent files created with the old Tails version are present in the filesystem 1.387
And all persistent directories from the old Tails version have safe access rights 2.379
After features/support/hooks.rb:330 0.946
After features/support/hooks.rb:100 0.009
6:16.493
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.567
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.071
And Tor is ready 20.344
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.352
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.078
Given I shutdown Tails and wait for the computer to power off 8.472
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.110
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.101
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.279
# 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.281
When the network is plugged 0.078
And Tor is ready 19.864
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.284
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.463
Given I shutdown Tails and wait for the computer to power off 4.240
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.774
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.996
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
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.272
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.075
And Tor is ready 16.896
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.241
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.866
After features/support/hooks.rb:330 0.878
After features/support/hooks.rb:100 0.019
35.251
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 9.580
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.504
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.115
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 18.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.292
After features/support/hooks.rb:330 0.740
After features/support/hooks.rb:100 0.000