Project Number Date
test_Tails_ISO_stable 5410 21 Jan 2025, 19:57

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:21.200 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:12.450
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 30.707
When I start Tails from USB drive "old" with network unplugged 1:36.068
Then the boot device has safe access rights 3.247
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.249
After features/support/hooks.rb:326 3.525
After features/support/hooks.rb:100 0.049
Tags: @product
2:9.743
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:25.241
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 33.189
And I take note of which tps features are available 1.368
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 8.601
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.668
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.966
Then Tails is running from USB drive "old" 2.500
And all tps features are active 3.271
When I write some files expected to persist 3.806
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.823
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.607
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 6.791
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.815
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.835
Before features/support/hooks.rb:269 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.829
And I log in to a new session 18.656
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.248
And I plug USB drive "to_upgrade" 2.361
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.148
Then the running Tails is installed on USB drive "to_upgrade" 24.130
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 2.465
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.425
Before features/support/hooks.rb:269 0.007
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.785
Then all tps features from the old Tails version are active 2.053
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.833
And the expected persistent files created with the old Tails version are present in the filesystem 1.535
And all persistent directories from the old Tails version have safe access rights 2.679
After features/support/hooks.rb:326 1.115
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:38.338
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 16.974
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.061
And Tor is ready 19.108
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.263
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.464
Given I shutdown Tails and wait for the computer to power off 8.702
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.506
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.024
And the file system changes introduced in version 6.2~testoverlayfs are present 0.353
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.276
# 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.373
When the network is plugged 0.066
And Tor is ready 18.804
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.222
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.387
Given I shutdown Tails and wait for the computer to power off 6.439
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.660
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.228
And the file system changes introduced in version 6.3~testoverlayfs are present 0.595
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.425
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.367
When the network is plugged 0.066
And Tor is ready 17.372
Then the Upgrader considers the system as up-to-date 10.816
# 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.260
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.066
After features/support/hooks.rb:326 0.745
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.738
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 10.211
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 19.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.381
After features/support/hooks.rb:326 0.689
After features/support/hooks.rb:100 0.000