Project Number Date
test_Tails_ISO_stable 5512 13 Mar 2025, 09:14

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:5.436 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.272
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.247
And I write an old version of the Tails USB image to disk "old" 1:8.963
When I start Tails from USB drive "old" with network unplugged 1:32.699
Then the boot device has safe access rights 3.096
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.542
After features/support/hooks.rb:100 0.014
Tags: @product
2:9.897
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:25.772
Then Tails is running from USB drive "old" 0.363
And I create a persistent partition 32.640
And I take note of which tps features are available 1.481
Then a Tails persistence partition exists on USB drive "old" 0.886
And I shutdown Tails and wait for the computer to power off 8.548
After features/support/hooks.rb:330 0.167
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.257
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.457
Then Tails is running from USB drive "old" 0.431
And all tps features are active 2.098
When I write some files expected to persist 2.504
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 3.991
And I take note of which tps features are available 0.416
And I shutdown Tails and wait for the computer to power off 6.775
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.679
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.739
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 9.819
And I log in to a new session 20.533
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.992
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.086
Then the running Tails is installed on USB drive "to_upgrade" 23.431
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:330 2.003
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.765
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.715
Then all tps features from the old Tails version are active 1.629
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.755
And the expected persistent files created with the old Tails version are present in the filesystem 1.453
And all persistent directories from the old Tails version have safe access rights 2.630
After features/support/hooks.rb:330 1.566
After features/support/hooks.rb:100 0.057
Tags: @product @automatic_upgrade
6:44.183
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 12.243
And no SquashFS delta is installed 0.757
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.295
When the network is plugged 0.117
And Tor is ready 21.696
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.932
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.138
Given I shutdown Tails and wait for the computer to power off 13.652
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.905
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.214
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.273
When the network is plugged 0.062
And Tor is ready 21.045
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.047
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.535
Given I shutdown Tails and wait for the computer to power off 4.355
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.096
Then Tails is running version 6.3~testoverlayfs 0.040
And all tps features are active 2.193
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.068
And Tor is ready 19.003
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.489
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.988
After features/support/hooks.rb:330 1.005
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.321
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.327
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the signing key used by the Upgrader is outdated 0.111
But a current signing key is available on our website 0.000
When the network is plugged 0.120
And Tor is ready 19.941
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.235
After features/support/hooks.rb:330 0.760
After features/support/hooks.rb:100 0.000