Project Number Date
test_Tails_ISO_stable 5035 19 Aug 2024, 12:09

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 18:35.957 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:2.890
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.657
When I start Tails from USB drive "old" with network unplugged 1:27.017
Then the boot device has safe access rights 3.003
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.696
After features/support/hooks.rb:100 0.010
Tags: @product
2:2.277
Before features/support/hooks.rb:269 0.007
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:20.030
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 31.322
And I take note of which tps features are available 1.474
Then a Tails persistence partition exists on USB drive "old" 0.725
And I shutdown Tails and wait for the computer to power off 8.199
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.320
Before features/support/hooks.rb:269 0.007
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.288
Then Tails is running from USB drive "old" 0.327
And all tps features are active 1.857
When I write some files expected to persist 1.614
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.487
And all persistent directories from the old Tails version have safe access rights 2.469
And I take note of which tps features are available 0.383
And I shutdown Tails and wait for the computer to power off 4.322
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.181
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.432
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.608
And I log in to a new session 17.881
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.791
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.473
Then the running Tails is installed on USB drive "to_upgrade" 17.858
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:326 7.245
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.767
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:3.988
Then all tps features from the old Tails version are active 1.406
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.003
And the expected persistent files created with the old Tails version are present in the filesystem 1.581
And all persistent directories from the old Tails version have safe access rights 2.297
After features/support/hooks.rb:326 0.730
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:29.543
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.634
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.072
And Tor is ready 20.421
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.067
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.389
Given I shutdown Tails and wait for the computer to power off 8.512
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.987
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.062
And the file system changes introduced in version 6.2~testoverlayfs are present 0.407
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.377
When the network is plugged 0.075
And Tor is ready 15.505
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.221
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.553
Given I shutdown Tails and wait for the computer to power off 4.409
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.859
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.900
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
And only the 6.3~testoverlayfs SquashFS delta is installed 0.112
# 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.606
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.362
When the network is plugged 0.088
And Tor is ready 17.334
Then the Upgrader considers the system as up-to-date 10.749
# 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.686
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.093
After features/support/hooks.rb:326 0.801
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
33.725
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.767
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.702
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 17.684
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.134
After features/support/hooks.rb:326 1.334
After features/support/hooks.rb:100 0.000