Project Number Date
test_Tails_ISO_tca-misc-improvements 3 10 Apr 2025, 20:03

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:43.408 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:4.975
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.471
When I start Tails from USB drive "old" with network unplugged 1:29.885
Then the boot device has safe access rights 3.339
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:330 7.157
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.486
And I start Tails from USB drive "old" with network unplugged and I login 1:25.519
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 30.966
And I take note of which tps features are available 2.512
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 8.875
After features/support/hooks.rb:330 0.245
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.815
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.144
Then Tails is running from USB drive "old" 0.333
And all tps features are active 2.144
When I write some files expected to persist 1.978
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.412
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.920
And I shutdown Tails and wait for the computer to power off 4.329
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.466
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.011
Tags: @product
2:34.030
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.819
And I log in to a new session 20.245
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.941
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.939
Then the running Tails is installed on USB drive "to_upgrade" 24.230
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 1.129
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.215
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.199
Then all tps features from the old Tails version are active 1.664
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.040
And the expected persistent files created with the old Tails version are present in the filesystem 1.408
And all persistent directories from the old Tails version have safe access rights 2.370
After features/support/hooks.rb:330 1.443
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:59.009
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.703
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.878
When the network is plugged 0.093
And Tor is ready 23.474
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.816
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.556
Given I shutdown Tails and wait for the computer to power off 8.738
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.545
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.334
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
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.411
# 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.366
When the network is plugged 0.065
And Tor is ready 18.027
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.540
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.148
Given I shutdown Tails and wait for the computer to power off 4.207
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.267
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.353
And the file system changes introduced in version 6.3~testoverlayfs are present 0.578
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.450
When the network is plugged 0.080
And Tor is ready 19.922
Then the Upgrader considers the system as up-to-date 0.316
# 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.767
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.770
After features/support/hooks.rb:330 0.777
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.764
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.304
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.097
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 21.644
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.385
After features/support/hooks.rb:330 1.234
After features/support/hooks.rb:100 0.000