Project Number Date
test_Tails_ISO_stable 5547 03 Apr 2025, 04:29

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:15.758 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:6.641
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.113
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.716
When I start Tails from USB drive "old" with network unplugged 1:31.533
Then the boot device has safe access rights 3.065
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.276
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:330 3.750
After features/support/hooks.rb:100 0.005
Tags: @product
2:4.166
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.144
And I start Tails from USB drive "old" with network unplugged and I login 1:22.568
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 30.776
And I take note of which tps features are available 1.354
Then a Tails persistence partition exists on USB drive "old" 0.753
And I shutdown Tails and wait for the computer to power off 8.259
After features/support/hooks.rb:330 0.150
After features/support/hooks.rb:100 0.006
Tags: @product
2:48.323
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.147
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.657
Then Tails is running from USB drive "old" 0.360
And all tps features are active 1.784
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.229
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.593
And I take note of which tps features are available 0.392
And I shutdown Tails and wait for the computer to power off 4.624
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.367
After features/support/hooks.rb:330 0.139
After features/support/hooks.rb:100 0.005
Tags: @product
2:30.185
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.813
And I log in to a new session 17.531
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.424
And I plug USB drive "to_upgrade" 2.489
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.960
Then the running Tails is installed on USB drive "to_upgrade" 21.556
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:330 2.188
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.942
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.150
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.570
Then all tps features from the old Tails version are active 1.630
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 3.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.435
And all persistent directories from the old Tails version have safe access rights 2.336
After features/support/hooks.rb:330 1.600
After features/support/hooks.rb:100 0.006
6:51.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.098
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.570
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.364
When the network is plugged 0.079
And Tor is ready 25.617
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.524
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.020
Given I shutdown Tails and wait for the computer to power off 8.570
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.401
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.053
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.300
When the network is plugged 0.078
And Tor is ready 46.749
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.572
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.541
Given I shutdown Tails and wait for the computer to power off 4.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.303
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.937
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.343
When the network is plugged 0.120
And Tor is ready 17.865
Then the Upgrader considers the system as up-to-date 0.310
# 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.338
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.466
After features/support/hooks.rb:330 0.928
After features/support/hooks.rb:100 0.013
38.872
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.924
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.513
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.090
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 21.649
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.541
After features/support/hooks.rb:330 0.699
After features/support/hooks.rb:100 0.000