Project Number Date
test_Tails_ISO_stable 5575 14 Apr 2025, 22:17

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:46.312 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:10.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.275
When I start Tails from USB drive "old" with network unplugged 1:35.128
Then the boot device has safe access rights 2.913
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.252
After features/support/hooks.rb:330 6.913
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.116
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:27.311
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 31.428
And I take note of which tps features are available 1.662
Then a Tails persistence partition exists on USB drive "old" 0.743
And I shutdown Tails and wait for the computer to power off 8.448
After features/support/hooks.rb:330 0.221
After features/support/hooks.rb:100 0.024
Tags: @product
3:0.034
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.107
Then Tails is running from USB drive "old" 1.577
And all tps features are active 2.228
When I write some files expected to persist 1.862
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.315
And all persistence configuration files have safe access rights 0.494
And all persistent directories from the old Tails version have safe access rights 5.037
And I take note of which tps features are available 0.810
And I shutdown Tails and wait for the computer to power off 6.311
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.064
After features/support/hooks.rb:330 0.172
After features/support/hooks.rb:100 0.011
Tags: @product
2:29.390
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 12.392
And I log in to a new session 19.175
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.436
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.829
Then the running Tails is installed on USB drive "to_upgrade" 20.710
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 1.184
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.054
Then all tps features from the old Tails version are active 1.634
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.504
And the expected persistent files created with the old Tails version are present in the filesystem 1.434
And all persistent directories from the old Tails version have safe access rights 2.544
After features/support/hooks.rb:330 1.316
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:51.694
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.162
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.609
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.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.068
And Tor is ready 20.270
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.489
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.856
Given I shutdown Tails and wait for the computer to power off 8.693
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.114
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.178
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
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.309
# 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.297
When the network is plugged 0.081
And Tor is ready 17.394
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.729
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.179
Given I shutdown Tails and wait for the computer to power off 4.284
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.183
Then Tails is running version 6.3~testoverlayfs 0.040
And all tps features are active 4.843
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.074
And Tor is ready 20.269
Then the Upgrader considers the system as up-to-date 0.314
# 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.398
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.377
After features/support/hooks.rb:330 0.801
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
37.686
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.041
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the signing key used by the Upgrader is outdated 0.101
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 19.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.601
After features/support/hooks.rb:330 0.961
After features/support/hooks.rb:100 0.000