Project Number Date
test_Tails_ISO_stable 5493 04 Mar 2025, 19:02

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:15.333 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.283
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.263
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.040
When I start Tails from USB drive "old" with network unplugged 1:31.905
Then the boot device has safe access rights 2.927
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:330 3.507
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.707
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:23.654
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 32.126
And I take note of which tps features are available 2.221
Then a Tails persistence partition exists on USB drive "old" 0.856
And I shutdown Tails and wait for the computer to power off 8.298
After features/support/hooks.rb:330 0.222
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.558
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.704
Then Tails is running from USB drive "old" 0.505
And all tps features are active 3.019
When I write some files expected to persist 1.743
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 3.177
And I take note of which tps features are available 0.822
And I shutdown Tails and wait for the computer to power off 4.182
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.627
After features/support/hooks.rb:330 0.102
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.608
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.277
And I log in to a new session 19.196
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.667
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.312
Then the running Tails is installed on USB drive "to_upgrade" 22.233
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.282
After features/support/hooks.rb:330 2.399
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.552
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.485
Then all tps features from the old Tails version are active 1.886
And Tails is running from USB drive "to_upgrade" 0.414
And the boot device has safe access rights 3.597
And the expected persistent files created with the old Tails version are present in the filesystem 1.516
And all persistent directories from the old Tails version have safe access rights 2.469
After features/support/hooks.rb:330 1.414
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:33.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.982
And no SquashFS delta is installed 0.856
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.413
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.437
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.497
When the network is plugged 0.062
And Tor is ready 21.410
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.612
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.724
Given I shutdown Tails and wait for the computer to power off 10.963
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.304
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.578
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.321
When the network is plugged 0.069
And Tor is ready 18.575
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.634
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.592
Given I shutdown Tails and wait for the computer to power off 4.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.380
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.964
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.086
And Tor is ready 15.381
Then the Upgrader considers the system as up-to-date 0.322
# 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.068
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.919
After features/support/hooks.rb:330 0.726
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.119
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.424
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.972
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.102
And Tor is ready 21.396
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.096
After features/support/hooks.rb:330 0.780
After features/support/hooks.rb:100 0.000