Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 33 07 Apr 2024, 06:18

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 16:38.126 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:32.621
Before features/support/hooks.rb:259 0.006
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 20.658
When I start Tails from USB drive "old" with network unplugged 1:6.820
Then the boot device has safe access rights 2.880
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:305 3.507
After features/support/hooks.rb:89 0.011
Tags: @product
1:55.832
Before features/support/hooks.rb:259 0.006
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:14.745
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 32.289
And I take note of which tps features are available 1.156
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 6.289
After features/support/hooks.rb:305 0.137
After features/support/hooks.rb:89 0.009
Tags: @product
2:27.669
Before features/support/hooks.rb:259 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:1.413
Then Tails is running from USB drive "old" 0.348
And all tps features are active 1.958
When I write some files expected to persist 1.609
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 2.288
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 4.347
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.534
After features/support/hooks.rb:305 0.188
After features/support/hooks.rb:89 0.009
Tags: @product
2:17.496
Before features/support/hooks.rb:259 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 9.483
And I log in to a new session 15.698
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.288
And I plug USB drive "to_upgrade" 2.410
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.392
Then the running Tails is installed on USB drive "to_upgrade" 12.864
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.164
After features/support/hooks.rb:305 6.429
After features/support/hooks.rb:89 0.000
Tags: @product
2:1.879
Before features/support/hooks.rb:259 0.007
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.962
Then all tps features from the old Tails version are active 1.487
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 2.961
And the expected persistent files created with the old Tails version are present in the filesystem 1.727
And all persistent directories from the old Tails version have safe access rights 2.214
After features/support/hooks.rb:305 0.939
After features/support/hooks.rb:89 0.009
5:49.855
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.810
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.050
And Tor is ready 17.647
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.282
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.992
Given I shutdown Tails and wait for the computer to power off 6.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.428
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.050
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.242
When the network is plugged 0.047
And Tor is ready 21.129
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.507
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.038
Given I shutdown Tails and wait for the computer to power off 4.274
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.286
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.010
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.055
And Tor is ready 15.566
Then the Upgrader considers the system as up-to-date 0.235
# 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 13.813
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.883
After features/support/hooks.rb:305 0.723
After features/support/hooks.rb:89 0.030
32.772
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.427
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.439
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 17.053
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.387
After features/support/hooks.rb:305 0.701
After features/support/hooks.rb:89 0.000