Project Number Date
test_Tails_ISO_tca-misc-improvements 14 21 Apr 2025, 18:52

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 20:22.092 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:24.360
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.627
When I start Tails from USB drive "old" with network unplugged 1:48.337
Then the boot device has safe access rights 3.037
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 3.925
After features/support/hooks.rb:100 0.011
Tags: @product
2:21.980
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.266
And I start Tails from USB drive "old" with network unplugged and I login 1:36.892
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 33.413
And I take note of which tps features are available 1.827
Then a Tails persistence partition exists on USB drive "old" 0.878
And I shutdown Tails and wait for the computer to power off 8.357
After features/support/hooks.rb:330 0.220
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.050
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.883
Then Tails is running from USB drive "old" 0.344
And all tps features are active 2.408
When I write some files expected to persist 1.757
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.865
And I take note of which tps features are available 0.752
And I shutdown Tails and wait for the computer to power off 6.552
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.686
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.364
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 13.782
And I log in to a new session 21.826
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.843
And I plug USB drive "to_upgrade" 2.649
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.966
Then the running Tails is installed on USB drive "to_upgrade" 27.843
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 1.529
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.710
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.004
Then all tps features from the old Tails version are active 1.608
And Tails is running from USB drive "to_upgrade" 0.453
And the boot device has safe access rights 3.461
And the expected persistent files created with the old Tails version are present in the filesystem 1.481
And all persistent directories from the old Tails version have safe access rights 2.500
After features/support/hooks.rb:330 1.418
After features/support/hooks.rb:100 0.011
6:56.264
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.358
And no SquashFS delta is installed 0.197
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.346
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.094
And Tor is ready 22.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.028
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.044
Given I shutdown Tails and wait for the computer to power off 11.238
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.951
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.635
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.325
When the network is plugged 0.085
And Tor is ready 19.919
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.574
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.959
Given I shutdown Tails and wait for the computer to power off 7.258
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.351
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.651
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.375
When the network is plugged 0.130
And Tor is ready 19.491
Then the Upgrader considers the system as up-to-date 0.342
# 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 16.047
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.786
After features/support/hooks.rb:330 0.687
After features/support/hooks.rb:100 0.020
39.362
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 12.847
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.470
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 18.549
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.210
After features/support/hooks.rb:330 0.993
After features/support/hooks.rb:100 0.000