Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 19 24 Mar 2024, 06:25

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:53.614 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:46.602
Before features/support/hooks.rb:245 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 23.748
When I start Tails from USB drive "old" with network unplugged 1:17.572
Then the boot device has safe access rights 2.993
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:291 7.264
After features/support/hooks.rb:75 0.010
Tags: @product
1:57.511
Before features/support/hooks.rb:245 0.007
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:16.028
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 32.755
And I take note of which tps features are available 1.496
Then a Tails persistence partition exists on USB drive "old" 0.728
And I shutdown Tails and wait for the computer to power off 6.020
After features/support/hooks.rb:291 0.130
After features/support/hooks.rb:75 0.010
Tags: @product
2:27.768
Before features/support/hooks.rb:245 0.006
Given a computer 0.295
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.711
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.026
When I write some files expected to persist 1.746
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.296
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.646
And I take note of which tps features are available 0.420
And I shutdown Tails and wait for the computer to power off 4.127
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.697
After features/support/hooks.rb:291 0.168
After features/support/hooks.rb:75 0.009
Tags: @product
2:21.744
Before features/support/hooks.rb:245 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 12.828
And I log in to a new session 16.455
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.513
And I plug USB drive "to_upgrade" 2.371
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.752
Then the running Tails is installed on USB drive "to_upgrade" 12.417
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:291 3.522
After features/support/hooks.rb:75 0.000
Tags: @product
2:0.976
Before features/support/hooks.rb:245 0.004
Given a computer 0.232
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.138
Then all tps features from the old Tails version are active 1.467
And Tails is running from USB drive "to_upgrade" 0.287
And the boot device has safe access rights 3.226
And the expected persistent files created with the old Tails version are present in the filesystem 1.314
And all persistent directories from the old Tails version have safe access rights 2.309
After features/support/hooks.rb:291 0.615
After features/support/hooks.rb:75 0.009
5:46.386
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.100
And no SquashFS delta is installed 0.194
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.487
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.072
And Tor is ready 15.862
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.580
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.773
Given I shutdown Tails and wait for the computer to power off 6.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.355
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 1.971
And the file system changes introduced in version 6.2~testoverlayfs are present 0.281
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.353
# 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.249
When the network is plugged 0.038
And Tor is ready 15.406
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.690
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.054
Given I shutdown Tails and wait for the computer to power off 4.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.606
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.877
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.033
And Tor is ready 19.183
Then the Upgrader considers the system as up-to-date 0.256
# 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 12.910
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.918
After features/support/hooks.rb:291 0.705
After features/support/hooks.rb:75 0.020
32.624
Before features/support/hooks.rb:245 0.033
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.152
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.367
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.595
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 16.635
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.782
After features/support/hooks.rb:291 1.047
After features/support/hooks.rb:75 0.000