Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 21 26 Mar 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 17:42.394 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:48.558
Before features/support/hooks.rb:245 0.006
Given a computer 0.271
And I create a 7200 MiB disk named "old" 0.088
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 28.947
When I start Tails from USB drive "old" with network unplugged 1:14.176
Then the boot device has safe access rights 3.072
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:291 7.337
After features/support/hooks.rb:75 0.011
Tags: @product
2:2.101
Before features/support/hooks.rb:245 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:17.692
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 34.159
And I take note of which tps features are available 1.550
Then a Tails persistence partition exists on USB drive "old" 0.974
And I shutdown Tails and wait for the computer to power off 7.138
After features/support/hooks.rb:291 0.205
After features/support/hooks.rb:75 0.010
Tags: @product
2:34.055
Before features/support/hooks.rb:245 0.006
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.675
Then Tails is running from USB drive "old" 0.494
And all tps features are active 2.170
When I write some files expected to persist 1.815
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.338
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.792
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 4.178
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.469
After features/support/hooks.rb:291 0.149
After features/support/hooks.rb:75 0.011
Tags: @product
2:29.354
Before features/support/hooks.rb:245 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 12.386
And I log in to a new session 20.898
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.972
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.232
Then the running Tails is installed on USB drive "to_upgrade" 14.032
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:291 3.580
After features/support/hooks.rb:75 0.000
Tags: @product
2:6.168
Before features/support/hooks.rb:245 0.009
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.245
Then all tps features from the old Tails version are active 1.739
And Tails is running from USB drive "to_upgrade" 0.401
And the boot device has safe access rights 3.665
And the expected persistent files created with the old Tails version are present in the filesystem 1.585
And all persistent directories from the old Tails version have safe access rights 2.328
After features/support/hooks.rb:291 1.061
After features/support/hooks.rb:75 0.010
6:6.537
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.345
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.035
And Tor is ready 20.205
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.042
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.878
Given I shutdown Tails and wait for the computer to power off 6.098
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.018
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.959
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.358
# 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.260
When the network is plugged 0.036
And Tor is ready 16.829
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.856
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.588
Given I shutdown Tails and wait for the computer to power off 5.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.582
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.309
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.047
And Tor is ready 18.954
Then the Upgrader considers the system as up-to-date 0.245
# 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.718
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.990
After features/support/hooks.rb:291 0.851
After features/support/hooks.rb:75 0.024
35.618
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.667
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.696
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 15.330
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.559
After features/support/hooks.rb:291 0.711
After features/support/hooks.rb:75 0.000