Project Number Date
test_Tails_ISO_stable 5085 09 Sep 2024, 13:58

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:18.820 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:45.362
Before features/support/hooks.rb:269 0.007
Given a computer 0.306
And I create a 7200 MiB disk named "old" 0.076
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 1:9.043
When I start Tails from USB drive "old" with network unplugged 1:30.662
Then the boot device has safe access rights 3.186
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 7.268
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.776
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:23.701
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 32.693
And I take note of which tps features are available 1.699
Then a Tails persistence partition exists on USB drive "old" 0.774
And I shutdown Tails and wait for the computer to power off 8.373
After features/support/hooks.rb:326 0.166
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.151
Before features/support/hooks.rb:269 0.007
Given a computer 0.311
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.632
Then Tails is running from USB drive "old" 0.414
And all tps features are active 2.428
When I write some files expected to persist 2.203
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.659
And I take note of which tps features are available 0.587
And I shutdown Tails and wait for the computer to power off 4.121
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.104
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.676
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 11.462
And I log in to a new session 20.344
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.619
And I plug USB drive "to_upgrade" 2.437
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.169
Then the running Tails is installed on USB drive "to_upgrade" 21.208
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 2.552
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.344
Before features/support/hooks.rb:269 0.008
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.075
Then all tps features from the old Tails version are active 1.625
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.140
And the expected persistent files created with the old Tails version are present in the filesystem 1.508
And all persistent directories from the old Tails version have safe access rights 2.453
After features/support/hooks.rb:326 0.840
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:0.618
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 11.352
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.372
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.079
And Tor is ready 21.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.801
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.515
Given I shutdown Tails and wait for the computer to power off 9.053
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.800
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.305
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.301
When the network is plugged 0.105
And Tor is ready 45.723
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.603
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.663
Given I shutdown Tails and wait for the computer to power off 6.658
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.676
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.219
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
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.475
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.341
When the network is plugged 0.092
And Tor is ready 19.630
Then the Upgrader considers the system as up-to-date 0.425
# 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 16.199
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.171
After features/support/hooks.rb:326 0.930
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
37.890
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 10.786
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 1.091
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 18.546
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.995
After features/support/hooks.rb:326 1.220
After features/support/hooks.rb:100 0.000