Project Number Date
test_Tails_ISO_stable 5393 15 Jan 2025, 12:48

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:44.387 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
1:54.103
Before features/support/hooks.rb:269 0.009
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 27.743
When I start Tails from USB drive "old" with network unplugged 1:20.804
Then the boot device has safe access rights 3.292
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.539
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.027
Before features/support/hooks.rb:269 0.005
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:21.081
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 30.655
And I take note of which tps features are available 1.328
Then a Tails persistence partition exists on USB drive "old" 0.799
And I shutdown Tails and wait for the computer to power off 6.651
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.008
Tags: @product
2:45.089
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.736
Then Tails is running from USB drive "old" 0.355
And all tps features are active 1.952
When I write some files expected to persist 1.762
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.302
And all persistence configuration files have safe access rights 0.497
And all persistent directories from the old Tails version have safe access rights 2.199
And I take note of which tps features are available 0.412
And I shutdown Tails and wait for the computer to power off 4.306
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.378
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.743
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.993
And I log in to a new session 22.150
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.653
And I plug USB drive "to_upgrade" 2.406
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.755
Then the running Tails is installed on USB drive "to_upgrade" 24.369
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 2.791
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.228
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.228
Then all tps features from the old Tails version are active 1.602
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 2.999
And the expected persistent files created with the old Tails version are present in the filesystem 1.401
And all persistent directories from the old Tails version have safe access rights 2.480
After features/support/hooks.rb:326 0.582
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:15.619
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 13.438
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.408
When the network is plugged 0.064
And Tor is ready 19.756
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.654
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.512
Given I shutdown Tails and wait for the computer to power off 8.551
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.443
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.026
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.378
When the network is plugged 0.084
And Tor is ready 18.398
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.265
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.883
Given I shutdown Tails and wait for the computer to power off 4.095
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.523
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.144
And the file system changes introduced in version 6.3~testoverlayfs are present 0.555
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.064
And Tor is ready 16.975
Then the Upgrader considers the system as up-to-date 0.352
# 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.887
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.024
After features/support/hooks.rb:326 0.728
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
1:4.575
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.556
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 49.939
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.603
After features/support/hooks.rb:326 0.655
After features/support/hooks.rb:100 0.000