Project Number Date
test_Tails_ISO_stable 5643 13 May 2025, 09:13

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:1.042 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:16.781
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
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" 35.150
When I start Tails from USB drive "old" with network unplugged 1:36.078
Then the boot device has safe access rights 3.270
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 3.535
After features/support/hooks.rb:100 0.023
Tags: @product
2:10.681
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:26.590
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 31.938
And I take note of which tps features are available 2.113
Then a Tails persistence partition exists on USB drive "old" 0.850
And I shutdown Tails and wait for the computer to power off 8.635
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.008
Tags: @product
3:4.407
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.374
Then Tails is running from USB drive "old" 1.014
And all tps features are active 2.244
When I write some files expected to persist 3.277
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.345
And I take note of which tps features are available 0.544
And I shutdown Tails and wait for the computer to power off 6.383
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.409
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.007
Tags: @product
2:37.043
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.391
And I log in to a new session 20.287
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.502
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.538
Then the running Tails is installed on USB drive "to_upgrade" 26.422
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:330 2.325
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.065
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.133
Then all tps features from the old Tails version are active 2.250
And Tails is running from USB drive "to_upgrade" 0.384
And the boot device has safe access rights 3.502
And the expected persistent files created with the old Tails version are present in the filesystem 1.489
And all persistent directories from the old Tails version have safe access rights 3.097
After features/support/hooks.rb:330 1.091
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:49.451
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.324
And no SquashFS delta is installed 0.348
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.667
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.346
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.487
When the network is plugged 0.117
And Tor is ready 20.706
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.282
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.116
Given I shutdown Tails and wait for the computer to power off 8.546
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.624
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.414
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.310
When the network is plugged 0.069
And Tor is ready 18.693
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.290
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.631
Given I shutdown Tails and wait for the computer to power off 6.595
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.807
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 4.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.357
When the network is plugged 0.068
And Tor is ready 18.958
Then the Upgrader considers the system as up-to-date 10.858
# 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.427
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.657
After features/support/hooks.rb:330 0.799
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
40.610
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.511
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.136
And the signing key used by the Upgrader is outdated 0.108
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 21.298
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.095
After features/support/hooks.rb:330 0.686
After features/support/hooks.rb:100 0.000