Project Number Date
test_Tails_ISO_stable 5682 28 May 2025, 13:07

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:13.225 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:6.357
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.934
When I start Tails from USB drive "old" with network unplugged 1:28.734
Then the boot device has safe access rights 3.362
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:330 7.282
After features/support/hooks.rb:100 0.013
Tags: @product
2:16.874
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:32.360
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 32.208
And I take note of which tps features are available 2.467
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 8.410
After features/support/hooks.rb:330 0.239
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.561
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.311
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.303
Then Tails is running from USB drive "old" 0.416
And all tps features are active 2.136
When I write some files expected to persist 2.296
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 2.651
And I take note of which tps features are available 0.659
And I shutdown Tails and wait for the computer to power off 6.901
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.213
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.018
Tags: @product
2:39.593
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.018
And I log in to a new session 19.606
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.037
And I plug USB drive "to_upgrade" 2.498
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.239
Then the running Tails is installed on USB drive "to_upgrade" 26.750
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:330 2.067
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.742
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.582
Then all tps features from the old Tails version are active 1.783
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.375
And the expected persistent files created with the old Tails version are present in the filesystem 1.638
And all persistent directories from the old Tails version have safe access rights 2.845
After features/support/hooks.rb:330 0.833
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:49.873
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.033
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.579
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.613
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.720
When the network is plugged 0.071
And Tor is ready 20.498
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.104
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.669
Given I shutdown Tails and wait for the computer to power off 9.185
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.823
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.541
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.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.284
When the network is plugged 0.064
And Tor is ready 19.754
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.402
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.256
Given I shutdown Tails and wait for the computer to power off 4.682
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.068
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.956
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.056
And Tor is ready 19.029
Then the Upgrader considers the system as up-to-date 0.412
# 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 17.095
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.429
After features/support/hooks.rb:330 0.846
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
58.223
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 10.601
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.649
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 46.062
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.641
After features/support/hooks.rb:330 0.976
After features/support/hooks.rb:100 0.000