Project Number Date
test_Tails_ISO_devel 3875 19 Jun 2025, 00:23

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 25:43.908 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:47.394
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 41.619
When I start Tails from USB drive "old" with network unplugged 1:59.568
Then the boot device has safe access rights 3.796
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 4.648
After features/support/hooks.rb:100 0.062
Tags: @product
2:54.156
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.063
Given a computer 1.360
And I start Tails from USB drive "old" with network unplugged and I login 1:55.339
Then Tails is running from USB drive "old" 2.412
And I create a persistent partition 42.224
And I take note of which tps features are available 3.183
Then a Tails persistence partition exists on USB drive "old" 1.187
And I shutdown Tails and wait for the computer to power off 8.448
After features/support/hooks.rb:330 0.213
After features/support/hooks.rb:100 0.009
Tags: @product
3:59.768
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.306
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:2.867
Then Tails is running from USB drive "old" 5.688
And all tps features are active 3.319
When I write some files expected to persist 2.088
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.384
And I take note of which tps features are available 0.625
And I shutdown Tails and wait for the computer to power off 9.831
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.971
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.012
Tags: @product
3:21.734
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 17.002
And I log in to a new session 23.726
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.772
And I plug USB drive "to_upgrade" 7.530
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:59.744
Then the running Tails is installed on USB drive "to_upgrade" 28.575
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:330 8.102
After features/support/hooks.rb:100 0.000
Tags: @product
3:3.351
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.597
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:44.451
Then all tps features from the old Tails version are active 1.990
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 4.562
And the expected persistent files created with the old Tails version are present in the filesystem 7.499
And all persistent directories from the old Tails version have safe access rights 3.896
After features/support/hooks.rb:330 0.926
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:42.937
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 17.486
And no SquashFS delta is installed 0.140
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.453
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.138
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.802
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.491
When the network is plugged 0.092
And Tor is ready 26.878
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.694
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.875
Given I shutdown Tails and wait for the computer to power off 13.420
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:41.997
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.244
And the file system changes introduced in version 6.2~testoverlayfs are present 0.388
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.421
# 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.385
When the network is plugged 0.078
And Tor is ready 29.448
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.903
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.038
Given I shutdown Tails and wait for the computer to power off 6.625
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:43.518
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 4.786
And the file system changes introduced in version 6.3~testoverlayfs are present 3.146
And only the 6.3~testoverlayfs SquashFS delta is installed 0.206
# 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.585
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.137
When the network is plugged 0.109
And Tor is ready 23.578
Then the Upgrader considers the system as up-to-date 0.348
# 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 21.319
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.078
After features/support/hooks.rb:330 0.792
After features/support/hooks.rb:100 0.047
Tags: @product @automatic_upgrade
54.565
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.597
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.118
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 26.088
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.417
After features/support/hooks.rb:330 1.422
After features/support/hooks.rb:100 0.000