Project Number Date
test_Tails_ISO_stable 5511 12 Mar 2025, 15:06

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.854 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:5.632
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.285
When I start Tails from USB drive "old" with network unplugged 1:28.518
Then the boot device has safe access rights 3.341
And Tails is running from USB drive "old" 0.416
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:330 7.044
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.086
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:32.276
Then Tails is running from USB drive "old" 0.402
And I create a persistent partition 31.411
And I take note of which tps features are available 1.409
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.550
After features/support/hooks.rb:330 0.207
After features/support/hooks.rb:100 0.012
Tags: @product
2:54.069
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.785
Then Tails is running from USB drive "old" 0.365
And all tps features are active 2.056
When I write some files expected to persist 1.737
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.503
And all persistent directories from the old Tails version have safe access rights 2.867
And I take note of which tps features are available 0.372
And I shutdown Tails and wait for the computer to power off 4.450
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.430
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.292
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 without a persistent partition and stopped at Tails Greeter's login screen 10.004
And I log in to a new session 19.556
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.967
And I plug USB drive "to_upgrade" 2.429
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.160
Then the running Tails is installed on USB drive "to_upgrade" 23.718
And I unplug USB drive "to_upgrade" 0.247
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 2.170
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.885
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.283
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.603
Then all tps features from the old Tails version are active 1.952
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 3.758
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.480
After features/support/hooks.rb:330 1.814
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:35.816
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 11.629
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.491
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.073
And Tor is ready 24.064
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.643
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.628
Given I shutdown Tails and wait for the computer to power off 10.865
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.572
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.275
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.270
When the network is plugged 0.059
And Tor is ready 18.583
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.691
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.426
Given I shutdown Tails and wait for the computer to power off 4.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.137
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.065
And the file system changes introduced in version 6.3~testoverlayfs are present 0.472
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.396
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.067
And Tor is ready 18.846
Then the Upgrader considers the system as up-to-date 0.331
# 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 14.875
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.949
After features/support/hooks.rb:330 0.768
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.070
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.222
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
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.115
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 19.782
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.451
After features/support/hooks.rb:330 1.008
After features/support/hooks.rb:100 0.000