Project Number Date
test_Tails_ISO_stable 4938 13 Jul 2024, 12:05

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:55.571 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:3.307
Before features/support/hooks.rb:269 0.006
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.048
When I start Tails from USB drive "old" with network unplugged 1:27.196
Then the boot device has safe access rights 2.839
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 3.745
After features/support/hooks.rb:100 0.011
Tags: @product
2:0.172
Before features/support/hooks.rb:269 0.007
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:18.730
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 30.487
And I take note of which tps features are available 1.235
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 8.388
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.010
Tags: @product
2:47.879
Before features/support/hooks.rb:269 0.007
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.526
Then Tails is running from USB drive "old" 0.316
And all tps features are active 1.792
When I write some files expected to persist 1.636
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.331
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.473
And I take note of which tps features are available 0.410
And I shutdown Tails and wait for the computer to power off 4.283
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.496
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.292
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.231
And I log in to a new session 17.492
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.319
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.316
Then the running Tails is installed on USB drive "to_upgrade" 18.098
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 1.851
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.292
Before features/support/hooks.rb:269 0.007
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.569
Then all tps features from the old Tails version are active 1.445
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.157
And the expected persistent files created with the old Tails version are present in the filesystem 1.381
And all persistent directories from the old Tails version have safe access rights 2.199
After features/support/hooks.rb:326 0.683
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:56.596
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.611
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.041
And Tor is ready 21.210
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.962
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.081
Given I shutdown Tails and wait for the computer to power off 8.403
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.672
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 1.949
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.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.282
When the network is plugged 0.051
And Tor is ready 20.432
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.782
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.870
Given I shutdown Tails and wait for the computer to power off 4.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.749
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 1.828
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.034
And Tor is ready 19.985
Then the Upgrader considers the system as up-to-date 0.317
# 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.039
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.901
After features/support/hooks.rb:326 0.732
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
34.030
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.359
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.848
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 18.414
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.931
After features/support/hooks.rb:326 0.667
After features/support/hooks.rb:100 0.000