Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 107 15 Jun 2024, 06:49

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 20:45.009 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:8.282
Before features/support/hooks.rb:269 0.005
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.254
When I start Tails from USB drive "old" with network unplugged 1:33.607
Then the boot device has safe access rights 3.086
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:320 3.952
After features/support/hooks.rb:100 0.050
Tags: @product
2:21.315
Before features/support/hooks.rb:269 0.032
Given a computer 0.475
And I start Tails from USB drive "old" with network unplugged and I login 1:33.709
Then Tails is running from USB drive "old" 0.424
And I create a persistent partition 35.573
And I take note of which tps features are available 1.640
Then a Tails persistence partition exists on USB drive "old" 0.854
And I shutdown Tails and wait for the computer to power off 8.638
After features/support/hooks.rb:320 0.159
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.999
Before features/support/hooks.rb:269 0.005
Given a computer 0.260
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.675
Then Tails is running from USB drive "old" 0.358
And all tps features are active 2.521
When I write some files expected to persist 1.836
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.885
And I take note of which tps features are available 2.731
And I shutdown Tails and wait for the computer to power off 4.515
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.594
After features/support/hooks.rb:320 0.165
After features/support/hooks.rb:100 0.016
Tags: @product
2:36.655
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.385
And I log in to a new session 18.427
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.350
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.330
Then the running Tails is installed on USB drive "to_upgrade" 24.201
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.292
After features/support/hooks.rb:320 2.293
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.001
Before features/support/hooks.rb:269 0.007
Given a computer 0.922
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.408
Then all tps features from the old Tails version are active 1.810
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.440
And the expected persistent files created with the old Tails version are present in the filesystem 1.490
And all persistent directories from the old Tails version have safe access rights 2.587
After features/support/hooks.rb:320 0.670
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:20.250
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.358
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.496
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.055
And Tor is ready 49.929
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.581
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.093
Given I shutdown Tails and wait for the computer to power off 8.663
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.417
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.528
And the file system changes introduced in version 6.2~testoverlayfs are present 0.359
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.397
# 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.272
When the network is plugged 0.054
And Tor is ready 20.855
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.392
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.534
Given I shutdown Tails and wait for the computer to power off 4.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.448
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.296
And the file system changes introduced in version 6.3~testoverlayfs are present 0.597
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.382
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.328
When the network is plugged 0.048
And Tor is ready 17.194
Then the Upgrader considers the system as up-to-date 10.914
# 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 14.772
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.596
After features/support/hooks.rb:320 1.518
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
40.505
Before features/support/hooks.rb:269 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.742
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 2.595
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 19.456
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.223
After features/support/hooks.rb:320 0.946
After features/support/hooks.rb:100 0.000