Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 13 14 Mar 2025, 01:19

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:17.566 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:2.886
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.831
When I start Tails from USB drive "old" with network unplugged 1:26.699
Then the boot device has safe access rights 3.030
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:330 3.515
After features/support/hooks.rb:100 0.044
Tags: @product
2:11.050
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 "old" with network unplugged and I login 1:24.227
Then Tails is running from USB drive "old" 0.397
And I create a persistent partition 35.015
And I take note of which tps features are available 1.764
Then a Tails persistence partition exists on USB drive "old" 0.906
And I shutdown Tails and wait for the computer to power off 8.559
After features/support/hooks.rb:330 0.221
After features/support/hooks.rb:100 0.012
Tags: @product
2:58.755
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.115
Then Tails is running from USB drive "old" 0.508
And all tps features are active 2.510
When I write some files expected to persist 1.846
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 2.667
And I take note of which tps features are available 1.487
And I shutdown Tails and wait for the computer to power off 4.182
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.542
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.706
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.086
And I log in to a new session 18.691
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.990
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.005
Then the running Tails is installed on USB drive "to_upgrade" 24.011
And I unplug USB drive "to_upgrade" 0.261
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 2.479
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.095
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 "to_upgrade" with network unplugged and I login with persistence enabled 2:4.704
Then all tps features from the old Tails version are active 1.836
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 3.623
And the expected persistent files created with the old Tails version are present in the filesystem 1.610
And all persistent directories from the old Tails version have safe access rights 2.730
After features/support/hooks.rb:330 1.354
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:40.102
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.354
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.476
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.541
When the network is plugged 0.068
And Tor is ready 17.875
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.153
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.312
Given I shutdown Tails and wait for the computer to power off 15.346
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.822
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.402
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.311
When the network is plugged 0.075
And Tor is ready 18.279
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.366
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.001
Given I shutdown Tails and wait for the computer to power off 4.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.804
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 3.067
And the file system changes introduced in version 6.3~testoverlayfs are present 0.548
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.314
When the network is plugged 0.096
And Tor is ready 17.721
Then the Upgrader considers the system as up-to-date 0.348
# 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.678
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.027
After features/support/hooks.rb:330 0.801
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.967
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.187
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.450
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 18.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.891
After features/support/hooks.rb:330 1.444
After features/support/hooks.rb:100 0.000