Project Number Date
test_Tails_ISO_stable 5315 05 Dec 2024, 12:26

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 19:26.457 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.344
Before features/support/hooks.rb:269 0.004
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.354
When I start Tails from USB drive "old" with network unplugged 1:32.268
Then the boot device has safe access rights 3.255
And Tails is running from USB drive "old" 0.396
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.280
After features/support/hooks.rb:326 3.523
After features/support/hooks.rb:100 0.017
Tags: @product
2:10.963
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:27.665
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 32.112
And I take note of which tps features are available 1.557
Then a Tails persistence partition exists on USB drive "old" 0.835
And I shutdown Tails and wait for the computer to power off 8.239
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.007
Tags: @product
2:53.529
Before features/support/hooks.rb:269 0.004
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.731
Then Tails is running from USB drive "old" 1.610
And all tps features are active 2.145
When I write some files expected to persist 1.584
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 3.822
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 5.155
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.194
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.631
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.319
And I log in to a new session 20.298
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.611
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.857
Then the running Tails is installed on USB drive "to_upgrade" 20.676
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.950
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.149
Before features/support/hooks.rb:269 0.007
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.522
Then all tps features from the old Tails version are active 1.649
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.103
And the expected persistent files created with the old Tails version are present in the filesystem 1.589
And all persistent directories from the old Tails version have safe access rights 2.694
After features/support/hooks.rb:326 0.649
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:49.021
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.635
And no SquashFS delta is installed 0.393
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.065
And Tor is ready 23.241
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.937
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.032
Given I shutdown Tails and wait for the computer to power off 8.863
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.172
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 2.270
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.313
When the network is plugged 0.071
And Tor is ready 21.646
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.016
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.774
Given I shutdown Tails and wait for the computer to power off 4.547
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.728
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.222
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
And only the 6.3~testoverlayfs SquashFS delta is installed 0.123
# 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.483
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.406
When the network is plugged 0.122
And Tor is ready 22.716
Then the Upgrader considers the system as up-to-date 0.344
# 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 15.503
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.759
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.818
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.146
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.524
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.920
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 21.352
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.738
After features/support/hooks.rb:326 0.688
After features/support/hooks.rb:100 0.000