Project Number Date
test_Tails_ISO_tca-misc-improvements 19 26 Apr 2025, 18:21

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 20:7.774 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:13.291
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.061
When I start Tails from USB drive "old" with network unplugged 1:35.651
Then the boot device has safe access rights 3.192
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.092
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:330 3.713
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.209
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:26.086
Then Tails is running from USB drive "old" 0.394
And I create a persistent partition 30.802
And I take note of which tps features are available 2.263
Then a Tails persistence partition exists on USB drive "old" 0.768
And I shutdown Tails and wait for the computer to power off 8.686
After features/support/hooks.rb:330 0.194
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.067
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.522
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.129
Then Tails is running from USB drive "old" 1.690
And all tps features are active 2.322
When I write some files expected to persist 2.951
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.447
And all persistent directories from the old Tails version have safe access rights 3.906
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 4.344
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.048
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.659
And I log in to a new session 19.326
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.547
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.948
Then the running Tails is installed on USB drive "to_upgrade" 25.364
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:330 0.953
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.901
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.252
Then all tps features from the old Tails version are active 1.774
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.453
And the expected persistent files created with the old Tails version are present in the filesystem 1.451
And all persistent directories from the old Tails version have safe access rights 2.475
After features/support/hooks.rb:330 1.136
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:5.964
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 with a persistent partition enabled and logged in 13.946
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.586
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.076
And Tor is ready 21.926
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.271
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.500
Given I shutdown Tails and wait for the computer to power off 8.509
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.459
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.230
And the file system changes introduced in version 6.2~testoverlayfs are present 0.384
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.494
# 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.272
When the network is plugged 0.088
And Tor is ready 18.271
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.777
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.337
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.890
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.931
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
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.291
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.082
And Tor is ready 19.601
Then the Upgrader considers the system as up-to-date 10.729
# 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.602
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.467
After features/support/hooks.rb:330 0.722
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
41.600
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.622
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.479
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
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.085
And Tor is ready 21.197
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.036
After features/support/hooks.rb:330 0.930
After features/support/hooks.rb:100 0.000