Project Number Date
test_Tails_ISO_tca-misc-improvements 20 27 Apr 2025, 18: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:52.363 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:38.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 36.267
When I start Tails from USB drive "old" with network unplugged 1:56.340
Then the boot device has safe access rights 3.259
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:330 3.728
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.205
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:25.647
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 31.744
And I take note of which tps features are available 2.078
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 8.386
After features/support/hooks.rb:330 0.173
After features/support/hooks.rb:100 0.007
Tags: @product
2:53.183
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.534
Then Tails is running from USB drive "old" 0.377
And all tps features are active 1.958
When I write some files expected to persist 2.073
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.453
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 4.370
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.075
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.221
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 11.990
And I log in to a new session 21.845
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.627
And I plug USB drive "to_upgrade" 2.523
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.429
Then the running Tails is installed on USB drive "to_upgrade" 25.363
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 2.208
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.364
Then all tps features from the old Tails version are active 1.846
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.724
And the expected persistent files created with the old Tails version are present in the filesystem 1.395
And all persistent directories from the old Tails version have safe access rights 2.561
After features/support/hooks.rb:330 1.382
After features/support/hooks.rb:100 0.008
6:38.192
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.862
And no SquashFS delta is installed 0.275
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.072
And Tor is ready 22.644
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.227
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.856
Given I shutdown Tails and wait for the computer to power off 8.676
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.492
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.337
And the file system changes introduced in version 6.2~testoverlayfs are present 0.395
And only the 6.2~testoverlayfs SquashFS delta is installed 0.116
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.406
# 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.303
When the network is plugged 0.067
And Tor is ready 18.686
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.494
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.611
Given I shutdown Tails and wait for the computer to power off 4.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.899
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.953
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.103
And Tor is ready 19.630
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 15.684
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.510
After features/support/hooks.rb:330 0.770
After features/support/hooks.rb:100 0.018
36.978
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 9.813
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.531
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.108
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 20.022
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.333
After features/support/hooks.rb:330 1.596
After features/support/hooks.rb:100 0.000