Project Number Date
test_Tails_ISO_stable 5347 19 Dec 2024, 12:58

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:53.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:8.265
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.647
When I start Tails from USB drive "old" with network unplugged 1:30.367
Then the boot device has safe access rights 2.982
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 0.940
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.904
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:35.069
Then Tails is running from USB drive "old" 0.399
And I create a persistent partition 31.537
And I take note of which tps features are available 1.731
Then a Tails persistence partition exists on USB drive "old" 0.739
And I shutdown Tails and wait for the computer to power off 8.244
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.007
Tags: @product
2:55.938
Before features/support/hooks.rb:269 0.004
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.988
Then Tails is running from USB drive "old" 0.320
And all tps features are active 2.020
When I write some files expected to persist 1.995
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.318
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 2.334
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 4.190
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.721
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.007
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 26.653
And I log in to a new session 20.490
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.647
And I plug USB drive "to_upgrade" 2.360
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.109
Then the running Tails is installed on USB drive "to_upgrade" 23.357
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:326 1.914
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.505
Before features/support/hooks.rb:269 0.008
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.148
Then all tps features from the old Tails version are active 1.632
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.079
And the expected persistent files created with the old Tails version are present in the filesystem 1.561
And all persistent directories from the old Tails version have safe access rights 2.545
After features/support/hooks.rb:326 0.635
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:41.315
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.354
And no SquashFS delta is installed 0.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.536
When the network is plugged 0.093
And Tor is ready 24.651
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.512
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.838
Given I shutdown Tails and wait for the computer to power off 11.187
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.559
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.347
And the file system changes introduced in version 6.2~testoverlayfs are present 0.400
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.542
# 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.287
When the network is plugged 0.072
And Tor is ready 19.661
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.215
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.134
Given I shutdown Tails and wait for the computer to power off 4.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.069
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.885
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.073
And Tor is ready 19.932
Then the Upgrader considers the system as up-to-date 0.319
# 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.223
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.007
After features/support/hooks.rb:326 0.773
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
43.472
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.430
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.468
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.920
But a current signing key is available on our website 0.000
When the network is plugged 0.109
And Tor is ready 25.255
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.234
After features/support/hooks.rb:326 0.648
After features/support/hooks.rb:100 0.000