Project Number Date
test_Tails_ISO_devel 3755 26 Mar 2025, 16:27

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:30.703 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:10.707
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.264
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 32.415
When I start Tails from USB drive "old" with network unplugged 1:32.648
Then the boot device has safe access rights 3.188
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 6.875
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.445
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:28.223
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 30.543
And I take note of which tps features are available 1.898
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.368
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.574
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.772
Then Tails is running from USB drive "old" 0.541
And all tps features are active 1.966
When I write some files expected to persist 2.041
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.308
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.902
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 6.542
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.453
After features/support/hooks.rb:330 0.106
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.993
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 11.571
And I log in to a new session 19.608
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.914
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.379
Then the running Tails is installed on USB drive "to_upgrade" 24.663
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:330 2.427
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.010
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.065
Then all tps features from the old Tails version are active 1.640
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.458
And the expected persistent files created with the old Tails version are present in the filesystem 1.666
And all persistent directories from the old Tails version have safe access rights 2.665
After features/support/hooks.rb:330 1.232
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:44.396
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 12.566
And no SquashFS delta is installed 0.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.069
And Tor is ready 20.494
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.321
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.722
Given I shutdown Tails and wait for the computer to power off 8.700
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.065
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.215
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.321
When the network is plugged 0.090
And Tor is ready 17.710
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.210
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.273
Given I shutdown Tails and wait for the computer to power off 4.590
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.737
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.131
And the file system changes introduced in version 6.3~testoverlayfs are present 0.716
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.288
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.105
And Tor is ready 17.965
Then the Upgrader considers the system as up-to-date 0.303
# 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.571
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.666
After features/support/hooks.rb:330 0.966
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
34.575
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 9.744
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.080
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 17.661
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.613
After features/support/hooks.rb:330 0.875
After features/support/hooks.rb:100 0.000