Project Number Date
test_Tails_ISO_devel 3854 04 Jun 2025, 13:46

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:28.143 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:32.388
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.352
And I create a 7200 MiB disk named "old" 0.615
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 33.473
When I start Tails from USB drive "old" with network unplugged 1:51.972
Then the boot device has safe access rights 3.655
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.431
And I unplug USB drive "old" 0.247
After features/support/hooks.rb:330 3.857
After features/support/hooks.rb:100 0.011
Tags: @product
2:15.670
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login 1:28.306
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 32.726
And I take note of which tps features are available 4.140
Then a Tails persistence partition exists on USB drive "old" 0.767
And I shutdown Tails and wait for the computer to power off 9.089
After features/support/hooks.rb:330 0.208
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.866
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.615
Then Tails is running from USB drive "old" 1.437
And all tps features are active 2.206
When I write some files expected to persist 2.748
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.827
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 6.602
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.148
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.370
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.752
And I log in to a new session 20.460
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.031
And I plug USB drive "to_upgrade" 2.384
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.406
Then the running Tails is installed on USB drive "to_upgrade" 23.906
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 7.013
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given a computer 0.267
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.265
Then all tps features from the old Tails version are active 1.915
And Tails is running from USB drive "to_upgrade" 0.379
And the boot device has safe access rights 3.874
And the expected persistent files created with the old Tails version are present in the filesystem 1.606
And all persistent directories from the old Tails version have safe access rights 2.715
After features/support/hooks.rb:330 1.318
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
6:52.549
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.498
And no SquashFS delta is installed 0.166
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
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.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.062
And Tor is ready 24.653
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.532
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.497
Given I shutdown Tails and wait for the computer to power off 12.203
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.453
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.581
And the file system changes introduced in version 6.2~testoverlayfs are present 0.401
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.326
# 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.328
When the network is plugged 0.096
And Tor is ready 19.157
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.302
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.246
Given I shutdown Tails and wait for the computer to power off 4.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.246
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.287
And the file system changes introduced in version 6.3~testoverlayfs are present 0.580
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.374
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.077
And Tor is ready 21.516
Then the Upgrader considers the system as up-to-date 0.354
# 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.300
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.116
After features/support/hooks.rb:330 0.743
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.275
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 with a persistent partition enabled and logged in 10.207
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.119
And the signing key used by the Upgrader is outdated 0.156
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 20.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.509
After features/support/hooks.rb:330 0.749
After features/support/hooks.rb:100 0.000