Project Number Date
test_Tails_ISO_stable 5281 21 Nov 2024, 08:54

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:4.710 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:9.858
Before features/support/hooks.rb:269 0.004
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.097
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.595
When I start Tails from USB drive "old" with network unplugged 1:32.639
Then the boot device has safe access rights 3.142
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.251
After features/support/hooks.rb:326 7.042
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.249
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:21.534
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 32.228
And I take note of which tps features are available 1.506
Then a Tails persistence partition exists on USB drive "old" 0.925
And I shutdown Tails and wait for the computer to power off 8.459
After features/support/hooks.rb:326 0.204
After features/support/hooks.rb:100 0.009
Tags: @product
3:4.044
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.269
Then Tails is running from USB drive "old" 0.921
And all tps features are active 2.187
When I write some files expected to persist 2.034
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.593
And all persistent directories from the old Tails version have safe access rights 2.496
And I take note of which tps features are available 0.398
And I shutdown Tails and wait for the computer to power off 4.343
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.330
After features/support/hooks.rb:326 0.115
After features/support/hooks.rb:100 0.012
Tags: @product
2:54.550
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 27.234
And I log in to a new session 26.195
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.837
And I plug USB drive "to_upgrade" 2.574
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.846
Then the running Tails is installed on USB drive "to_upgrade" 20.391
And I unplug USB drive "to_upgrade" 0.249
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 3.588
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.040
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.200
Then all tps features from the old Tails version are active 1.908
And Tails is running from USB drive "to_upgrade" 0.407
And the boot device has safe access rights 3.410
And the expected persistent files created with the old Tails version are present in the filesystem 1.386
And all persistent directories from the old Tails version have safe access rights 2.529
After features/support/hooks.rb:326 0.894
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:46.414
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.435
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
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.442
When the network is plugged 0.076
And Tor is ready 24.819
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.583
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.317
Given I shutdown Tails and wait for the computer to power off 11.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.422
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.709
And the file system changes introduced in version 6.2~testoverlayfs are present 0.388
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.382
# 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.319
When the network is plugged 0.065
And Tor is ready 19.282
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.636
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.111
Given I shutdown Tails and wait for the computer to power off 4.701
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.235
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.004
And the file system changes introduced in version 6.3~testoverlayfs are present 0.735
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.566
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.069
And Tor is ready 19.230
Then the Upgrader considers the system as up-to-date 0.400
# 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.658
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.324
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.089
Tags: @product @automatic_upgrade
45.551
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.358
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the signing key used by the Upgrader is outdated 1.461
But a current signing key is available on our website 0.000
When the network is plugged 0.973
And Tor is ready 23.991
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.231
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.000