Project Number Date
test_Tails_ISO_stable 5654 18 May 2025, 08:56

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:18.331 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:17.207
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 33.147
When I start Tails from USB drive "old" with network unplugged 1:38.748
Then the boot device has safe access rights 3.045
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 3.524
After features/support/hooks.rb:100 0.013
Tags: @product
2:5.571
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:24.092
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 30.112
And I take note of which tps features are available 1.722
Then a Tails persistence partition exists on USB drive "old" 0.733
And I shutdown Tails and wait for the computer to power off 8.378
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.602
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 with persistence enabled 2:11.384
Then Tails is running from USB drive "old" 0.405
And all tps features are active 2.145
When I write some files expected to persist 2.066
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.577
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 4.230
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.455
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.550
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.165
And I log in to a new session 20.013
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.705
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.555
Then the running Tails is installed on USB drive "to_upgrade" 24.275
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:330 2.904
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.806
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 "to_upgrade" with network unplugged and I login with persistence enabled 2:7.841
Then all tps features from the old Tails version are active 1.736
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 3.652
And the expected persistent files created with the old Tails version are present in the filesystem 1.494
And all persistent directories from the old Tails version have safe access rights 2.534
After features/support/hooks.rb:330 1.061
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:34.214
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 13.380
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.079
And Tor is ready 23.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.946
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.933
Given I shutdown Tails and wait for the computer to power off 8.688
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.562
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.110
And the file system changes introduced in version 6.2~testoverlayfs are present 0.368
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.357
# 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.295
When the network is plugged 0.076
And Tor is ready 20.438
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.044
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.995
Given I shutdown Tails and wait for the computer to power off 4.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.369
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.999
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.076
And Tor is ready 17.397
Then the Upgrader considers the system as up-to-date 0.357
# 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.453
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.454
After features/support/hooks.rb:330 0.819
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
37.377
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 10.825
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 19.156
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.858
After features/support/hooks.rb:330 0.821
After features/support/hooks.rb:100 0.000