Project Number Date
test_Tails_ISO_18215-update-chutney-force-all-tests 21 01 Apr 2025, 12:35

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:3.542 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:3.618
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.083
And I write an old version of the Tails USB image to disk "old" 29.844
When I start Tails from USB drive "old" with network unplugged 1:26.590
Then the boot device has safe access rights 4.593
And Tails is running from USB drive "old" 0.405
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.355
And I unplug USB drive "old" 0.304
After features/support/hooks.rb:330 3.702
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.353
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:23.361
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 32.463
And I take note of which tps features are available 1.657
Then a Tails persistence partition exists on USB drive "old" 0.895
And I shutdown Tails and wait for the computer to power off 8.460
After features/support/hooks.rb:330 0.138
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.979
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.631
Then Tails is running from USB drive "old" 0.498
And all tps features are active 2.105
When I write some files expected to persist 1.878
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 3.128
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.471
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.993
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.717
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.864
And I log in to a new session 18.330
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.144
And I plug USB drive "to_upgrade" 2.592
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.043
Then the running Tails is installed on USB drive "to_upgrade" 22.295
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.246
After features/support/hooks.rb:330 2.320
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.297
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:26.805
Then all tps features from the old Tails version are active 1.846
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.697
And the expected persistent files created with the old Tails version are present in the filesystem 1.695
And all persistent directories from the old Tails version have safe access rights 2.690
After features/support/hooks.rb:330 1.612
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:48.364
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.521
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.673
When the network is plugged 0.167
And Tor is ready 22.038
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.905
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.352
Given I shutdown Tails and wait for the computer to power off 9.091
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.712
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.490
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
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.310
# 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.280
When the network is plugged 0.081
And Tor is ready 18.431
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.714
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.802
Given I shutdown Tails and wait for the computer to power off 6.578
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.320
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.069
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.454
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.081
And Tor is ready 19.563
Then the Upgrader considers the system as up-to-date 0.332
# 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.711
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.621
After features/support/hooks.rb:330 0.901
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
57.209
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.261
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.614
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 0.149
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 45.427
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.589
After features/support/hooks.rb:330 0.722
After features/support/hooks.rb:100 0.000