Project Number Date
test_Tails_ISO_stable 5525 21 Mar 2025, 12: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 21:34.467 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:22.029
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.614
And I create a 7200 MiB disk named "old" 0.483
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 32.517
When I start Tails from USB drive "old" with network unplugged 1:43.353
Then the boot device has safe access rights 3.036
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 1.034
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.616
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:24.399
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 31.672
And I take note of which tps features are available 1.524
Then a Tails persistence partition exists on USB drive "old" 0.767
And I shutdown Tails and wait for the computer to power off 8.711
After features/support/hooks.rb:330 0.193
After features/support/hooks.rb:100 0.018
Tags: @product
3:11.939
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.305
Then Tails is running from USB drive "old" 0.344
And all tps features are active 2.129
When I write some files expected to persist 2.868
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.686
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 6.284
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.018
After features/support/hooks.rb:330 0.126
After features/support/hooks.rb:100 0.007
Tags: @product
2:47.226
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 without a persistent partition and stopped at Tails Greeter's login screen 24.257
And I log in to a new session 19.489
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.995
And I plug USB drive "to_upgrade" 2.551
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.158
Then the running Tails is installed on USB drive "to_upgrade" 24.335
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:330 1.928
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.190
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.150
Then all tps features from the old Tails version are active 1.730
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.534
And the expected persistent files created with the old Tails version are present in the filesystem 1.692
And all persistent directories from the old Tails version have safe access rights 2.498
After features/support/hooks.rb:330 1.507
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:55.137
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 11.100
And no SquashFS delta is installed 0.139
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.538
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.851
When the network is plugged 0.076
And Tor is ready 22.775
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.825
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.963
Given I shutdown Tails and wait for the computer to power off 1:22.186
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.936
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.353
And the file system changes introduced in version 6.2~testoverlayfs are present 0.353
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.266
# 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.296
When the network is plugged 0.067
And Tor is ready 18.917
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.857
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.259
Given I shutdown Tails and wait for the computer to power off 4.346
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.188
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.216
And the file system changes introduced in version 6.3~testoverlayfs are present 0.566
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.297
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.071
And Tor is ready 16.724
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 15.739
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.007
After features/support/hooks.rb:330 0.997
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
40.328
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.287
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.857
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.109
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 22.644
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.268
After features/support/hooks.rb:330 0.695
After features/support/hooks.rb:100 0.000