Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 85 26 May 2024, 06:56

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:50.980 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:15.050
Before features/support/hooks.rb:259 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.914
When I start Tails from USB drive "old" with network unplugged 1:36.609
Then the boot device has safe access rights 3.161
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.283
After features/support/hooks.rb:305 7.181
After features/support/hooks.rb:89 0.010
Tags: @product
2:25.258
Before features/support/hooks.rb:259 0.006
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 1:35.070
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 37.689
And I take note of which tps features are available 2.280
Then a Tails persistence partition exists on USB drive "old" 0.902
And I shutdown Tails and wait for the computer to power off 8.731
After features/support/hooks.rb:305 0.217
After features/support/hooks.rb:89 0.008
Tags: @product
2:56.536
Before features/support/hooks.rb:259 0.004
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.139
Then Tails is running from USB drive "old" 0.351
And all tps features are active 2.066
When I write some files expected to persist 1.837
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 3.025
And I take note of which tps features are available 0.486
And I shutdown Tails and wait for the computer to power off 4.240
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.471
After features/support/hooks.rb:305 0.170
After features/support/hooks.rb:89 0.009
Tags: @product
2:33.368
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.621
And I log in to a new session 21.960
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.930
And I plug USB drive "to_upgrade" 2.580
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.847
Then the running Tails is installed on USB drive "to_upgrade" 17.947
And I unplug USB drive "to_upgrade" 0.254
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:305 3.580
After features/support/hooks.rb:89 0.000
Tags: @product
2:27.188
Before features/support/hooks.rb:259 0.008
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.311
Then all tps features from the old Tails version are active 1.889
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.394
And the expected persistent files created with the old Tails version are present in the filesystem 1.569
And all persistent directories from the old Tails version have safe access rights 2.464
After features/support/hooks.rb:305 0.664
After features/support/hooks.rb:89 0.048
6:38.142
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.450
And no SquashFS delta is installed 0.262
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.038
And Tor is ready 21.510
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.645
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.583
Given I shutdown Tails and wait for the computer to power off 11.003
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.313
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.318
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
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.340
# 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.287
When the network is plugged 0.033
And Tor is ready 20.187
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.501
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.476
Given I shutdown Tails and wait for the computer to power off 4.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.055
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.221
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
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.371
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.038
And Tor is ready 19.953
Then the Upgrader considers the system as up-to-date 0.344
# 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.229
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.087
After features/support/hooks.rb:305 1.102
After features/support/hooks.rb:89 0.018
35.435
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.545
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.523
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 17.223
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.692
After features/support/hooks.rb:305 0.629
After features/support/hooks.rb:89 0.000