Project Number Date
test_Tails_ISO_stable 5399 16 Jan 2025, 20:34

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:25.770 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.519
Before features/support/hooks.rb:269 0.003
Given a computer 0.873
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.632
When I start Tails from USB drive "old" with network unplugged 1:30.626
Then the boot device has safe access rights 3.249
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:326 3.556
After features/support/hooks.rb:100 0.010
Tags: @product
2:18.751
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:29.400
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 37.455
And I take note of which tps features are available 1.951
Then a Tails persistence partition exists on USB drive "old" 0.815
And I shutdown Tails and wait for the computer to power off 8.603
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.007
Tags: @product
2:55.131
Before features/support/hooks.rb:269 0.003
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.941
Then Tails is running from USB drive "old" 0.535
And all tps features are active 1.986
When I write some files expected to persist 2.595
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.370
And all persistent directories from the old Tails version have safe access rights 2.566
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 4.447
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.875
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.012
Tags: @product
2:37.210
Before features/support/hooks.rb:269 0.022
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.161
And I log in to a new session 19.206
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.207
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.669
Then the running Tails is installed on USB drive "to_upgrade" 25.095
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 3.620
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.093
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.204
Then all tps features from the old Tails version are active 1.677
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.317
And the expected persistent files created with the old Tails version are present in the filesystem 1.578
And all persistent directories from the old Tails version have safe access rights 2.770
After features/support/hooks.rb:326 0.727
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:35.268
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.955
And no SquashFS delta is installed 0.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.385
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.405
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.069
And Tor is ready 21.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.767
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.900
Given I shutdown Tails and wait for the computer to power off 8.539
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.182
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.197
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.297
When the network is plugged 0.073
And Tor is ready 18.522
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.873
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.514
Given I shutdown Tails and wait for the computer to power off 1:0.942
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.970
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.178
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.083
And Tor is ready 18.868
Then the Upgrader considers the system as up-to-date 0.340
# 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 14.439
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.975
After features/support/hooks.rb:326 0.827
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.795
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 9.777
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.563
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 20.908
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.292
After features/support/hooks.rb:326 0.714
After features/support/hooks.rb:100 0.000