Project Number Date
test_Tails_ISO_devel 3906 15 Jul 2025, 16: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 37:22.029 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
3:37.082
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 57.316
When I start Tails from USB drive "old" with network unplugged 2:22.523
Then the boot device has safe access rights 4.213
And Tails is running from USB drive "old" 6.015
And there is no persistence partition on USB drive "old" 2.313
And process "udev-watchdog" is running 0.649
And udev-watchdog is monitoring the correct device 1.652
And I unplug USB drive "old" 1.090
After features/support/hooks.rb:330 4.001
After features/support/hooks.rb:100 0.037
Tags: @product
4:12.543
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.268
And I start Tails from USB drive "old" with network unplugged and I login 2:45.650
Then Tails is running from USB drive "old" 5.578
And I create a persistent partition 1:2.122
And I take note of which tps features are available 4.150
Then a Tails persistence partition exists on USB drive "old" 0.902
And I shutdown Tails and wait for the computer to power off 13.871
After features/support/hooks.rb:330 2.782
After features/support/hooks.rb:100 0.092
Tags: @product
5:58.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Given a computer 0.706
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:30.888
Then Tails is running from USB drive "old" 3.562
And all tps features are active 6.837
When I write some files expected to persist 1.829
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.283
And all persistence configuration files have safe access rights 0.660
And all persistent directories from the old Tails version have safe access rights 3.567
And I take note of which tps features are available 0.574
And I shutdown Tails and wait for the computer to power off 12.858
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 56.820
After features/support/hooks.rb:330 0.632
After features/support/hooks.rb:100 0.050
Tags: @product
4:3.612
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.043
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 18.722
And I log in to a new session 33.776
And I clone USB drive "old" to a new USB drive "to_upgrade" 10.637
And I plug USB drive "to_upgrade" 3.030
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:2.588
Then the running Tails is installed on USB drive "to_upgrade" 54.438
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:330 5.241
After features/support/hooks.rb:100 0.000
Tags: @product
4:26.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:5.278
Then all tps features from the old Tails version are active 6.521
And Tails is running from USB drive "to_upgrade" 0.546
And the boot device has safe access rights 3.979
And the expected persistent files created with the old Tails version are present in the filesystem 2.111
And all persistent directories from the old Tails version have safe access rights 7.561
After features/support/hooks.rb:330 2.145
After features/support/hooks.rb:100 0.085
Tags: @product @automatic_upgrade
13:24.601
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.058
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 43.425
And no SquashFS delta is installed 0.218
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.760
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.360
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.550
When the network is plugged 0.100
And Tor is ready 36.601
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.307
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 22.636
Given I shutdown Tails and wait for the computer to power off 16.532
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:51.498
Then Tails is running version 6.2~testoverlayfs 0.372
And all tps features are active 6.592
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.069
And Tor is ready 39.749
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.298
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 33.590
Given I shutdown Tails and wait for the computer to power off 6.454
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:57.524
Then Tails is running version 6.3~testoverlayfs 0.064
And all tps features are active 9.446
And the file system changes introduced in version 6.3~testoverlayfs are present 6.293
And only the 6.3~testoverlayfs SquashFS delta is installed 0.190
# 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.450
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.467
When the network is plugged 0.092
And Tor is ready 42.972
Then the Upgrader considers the system as up-to-date 1.055
# 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 41.263
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 13.537
After features/support/hooks.rb:330 1.026
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
1:39.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 30.972
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 6.108
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.523
And the signing key used by the Upgrader is outdated 0.352
But a current signing key is available on our website 0.000
When the network is plugged 0.299
And Tor is ready 54.366
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.751
After features/support/hooks.rb:330 1.138
After features/support/hooks.rb:100 0.000