Project Number Date
test_Tails_ISO_devel 3787 24 Apr 2025, 21:55

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:24.278 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.136
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 33.031
When I start Tails from USB drive "old" with network unplugged 1:27.734
Then the boot device has safe access rights 3.065
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 3.928
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.456
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.643
And I start Tails from USB drive "old" with network unplugged and I login 1:26.262
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 31.434
And I take note of which tps features are available 2.337
Then a Tails persistence partition exists on USB drive "old" 0.860
And I shutdown Tails and wait for the computer to power off 6.589
After features/support/hooks.rb:330 0.184
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.543
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.885
Then Tails is running from USB drive "old" 0.527
And all tps features are active 2.012
When I write some files expected to persist 1.821
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.653
And I take note of which tps features are available 0.395
And I shutdown Tails and wait for the computer to power off 6.407
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.971
After features/support/hooks.rb:330 0.125
After features/support/hooks.rb:100 0.008
Tags: @product
2:42.102
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 13.220
And I log in to a new session 21.960
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.028
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.277
Then the running Tails is installed on USB drive "to_upgrade" 27.700
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:330 3.018
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.992
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.437
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.011
Then all tps features from the old Tails version are active 1.631
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.602
And the expected persistent files created with the old Tails version are present in the filesystem 1.496
And all persistent directories from the old Tails version have safe access rights 2.473
After features/support/hooks.rb:330 1.132
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:40.291
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 11.496
And no SquashFS delta is installed 0.274
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.453
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.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.126
And Tor is ready 21.399
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.899
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.143
Given I shutdown Tails and wait for the computer to power off 11.018
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.156
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.123
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.299
When the network is plugged 0.063
And Tor is ready 20.909
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.693
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.611
Given I shutdown Tails and wait for the computer to power off 4.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.300
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.345
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.399
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.406
When the network is plugged 0.077
And Tor is ready 17.202
Then the Upgrader considers the system as up-to-date 0.357
# 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.608
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.516
After features/support/hooks.rb:330 0.847
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.755
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 9.292
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.105
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 22.135
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.719
After features/support/hooks.rb:330 1.143
After features/support/hooks.rb:100 0.000