Project Number Date
test_Tails_ISO_devel 3705 21 Feb 2025, 16:37

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:31.506 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:6.263
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.425
When I start Tails from USB drive "old" with network unplugged 1:29.519
Then the boot device has safe access rights 3.066
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:330 3.530
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.998
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:22.470
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 31.413
And I take note of which tps features are available 1.452
Then a Tails persistence partition exists on USB drive "old" 0.758
And I shutdown Tails and wait for the computer to power off 8.361
After features/support/hooks.rb:330 0.254
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.183
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.455
Then Tails is running from USB drive "old" 1.155
And all tps features are active 2.037
When I write some files expected to persist 1.619
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.316
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 3.202
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.366
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.940
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.487
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 11.099
And I log in to a new session 18.646
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.506
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.430
Then the running Tails is installed on USB drive "to_upgrade" 17.992
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 2.160
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.351
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.269
Then all tps features from the old Tails version are active 1.626
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.176
And the expected persistent files created with the old Tails version are present in the filesystem 1.502
And all persistent directories from the old Tails version have safe access rights 2.279
After features/support/hooks.rb:330 1.091
After features/support/hooks.rb:100 0.009
6:22.580
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 11.071
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.529
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.060
And Tor is ready 20.920
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.425
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.797
Given I shutdown Tails and wait for the computer to power off 8.511
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.367
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.266
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.292
When the network is plugged 0.081
And Tor is ready 16.108
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.469
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.186
Given I shutdown Tails and wait for the computer to power off 4.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.463
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.988
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.287
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.069
And Tor is ready 19.150
Then the Upgrader considers the system as up-to-date 0.322
# 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.570
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.948
After features/support/hooks.rb:330 0.697
After features/support/hooks.rb:100 0.015
35.641
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.946
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.687
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.126
And the signing key used by the Upgrader is outdated 0.108
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 19.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.041
After features/support/hooks.rb:330 0.787
After features/support/hooks.rb:100 0.000