Project Number Date
test_Tails_ISO_stable 5509 12 Mar 2025, 10:28

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:16.347 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:4.192
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.756
When I start Tails from USB drive "old" with network unplugged 1:27.031
Then the boot device has safe access rights 3.078
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:330 3.553
After features/support/hooks.rb:100 0.011
Tags: @product
2:6.809
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:23.061
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 32.090
And I take note of which tps features are available 1.699
Then a Tails persistence partition exists on USB drive "old" 0.860
And I shutdown Tails and wait for the computer to power off 8.567
After features/support/hooks.rb:330 0.174
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.198
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.570
Then Tails is running from USB drive "old" 0.864
And all tps features are active 2.001
When I write some files expected to persist 2.119
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 3.649
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 4.478
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.183
After features/support/hooks.rb:330 0.139
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.164
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 10.992
And I log in to a new session 19.493
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.949
And I plug USB drive "to_upgrade" 2.447
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.471
Then the running Tails is installed on USB drive "to_upgrade" 23.389
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:330 2.246
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.952
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.310
Then all tps features from the old Tails version are active 1.614
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.238
And the expected persistent files created with the old Tails version are present in the filesystem 1.625
And all persistent directories from the old Tails version have safe access rights 2.628
After features/support/hooks.rb:330 1.328
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:38.535
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 with a persistent partition enabled and logged in 14.260
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.656
When the network is plugged 0.067
And Tor is ready 22.071
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.464
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.002
Given I shutdown Tails and wait for the computer to power off 13.607
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.015
Then Tails is running version 6.2~testoverlayfs 0.037
And all tps features are active 2.362
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
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.286
# 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.277
When the network is plugged 0.121
And Tor is ready 18.488
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.432
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.847
Given I shutdown Tails and wait for the computer to power off 4.357
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.966
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.905
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.255
When the network is plugged 0.075
And Tor is ready 21.208
Then the Upgrader considers the system as up-to-date 0.320
# 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.230
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.059
After features/support/hooks.rb:330 0.874
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
37.495
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 with a persistent partition enabled and logged in 10.073
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.113
And the signing key used by the Upgrader is outdated 0.125
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 21.532
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.194
After features/support/hooks.rb:330 0.663
After features/support/hooks.rb:100 0.000