Project Number Date
test_Tails_ISO_20861-allow-close-zenity-exit-code 2 31 Mar 2025, 20:30

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:32.648 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:11.788
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.018
When I start Tails from USB drive "old" with network unplugged 1:35.150
Then the boot device has safe access rights 3.229
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 3.725
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.370
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 "old" with network unplugged and I login 1:21.660
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 33.416
And I take note of which tps features are available 1.564
Then a Tails persistence partition exists on USB drive "old" 0.793
And I shutdown Tails and wait for the computer to power off 8.432
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.007
Tags: @product
2:55.008
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.372
Then Tails is running from USB drive "old" 1.486
And all tps features are active 2.052
When I write some files expected to persist 1.778
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 3.461
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 6.603
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.862
After features/support/hooks.rb:330 0.133
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.392
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.465
And I log in to a new session 20.835
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.484
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.433
Then the running Tails is installed on USB drive "to_upgrade" 25.338
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 6.555
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.767
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.588
Then all tps features from the old Tails version are active 1.591
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.308
And the expected persistent files created with the old Tails version are present in the filesystem 1.372
And all persistent directories from the old Tails version have safe access rights 2.363
After features/support/hooks.rb:330 1.587
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:19.092
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 11.505
And no SquashFS delta is installed 0.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.743
When the network is plugged 0.255
And Tor is ready 24.525
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.022
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.487
Given I shutdown Tails and wait for the computer to power off 8.714
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.633
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.297
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.281
# 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.327
When the network is plugged 0.076
And Tor is ready 18.087
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.556
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.475
Given I shutdown Tails and wait for the computer to power off 4.491
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.809
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 3.698
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.085
And Tor is ready 48.280
Then the Upgrader considers the system as up-to-date 0.329
# 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 16.080
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.728
After features/support/hooks.rb:330 0.763
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
57.228
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 with a persistent partition enabled and logged in 10.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.520
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.143
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 45.685
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.665
After features/support/hooks.rb:330 1.086
After features/support/hooks.rb:100 0.000