Project Number Date
test_Tails_ISO_stable 5351 22 Dec 2024, 12:43

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 18:46.342 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:4.941
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.737
When I start Tails from USB drive "old" with network unplugged 1:29.008
Then the boot device has safe access rights 2.928
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.126
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.546
After features/support/hooks.rb:100 0.007
Tags: @product
2:5.618
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:24.443
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 29.764
And I take note of which tps features are available 1.801
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 8.305
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.966
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.995
Then Tails is running from USB drive "old" 0.847
And all tps features are active 1.963
When I write some files expected to persist 1.635
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.734
And all persistent directories from the old Tails version have safe access rights 2.452
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.543
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.964
After features/support/hooks.rb:326 0.098
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.931
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.096
And I log in to a new session 18.203
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.527
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.602
Then the running Tails is installed on USB drive "to_upgrade" 16.680
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 7.445
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.798
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.292
Then all tps features from the old Tails version are active 1.657
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.375
And the expected persistent files created with the old Tails version are present in the filesystem 1.487
And all persistent directories from the old Tails version have safe access rights 2.463
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:24.548
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 13.065
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
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.407
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.079
And Tor is ready 22.710
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.569
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.413
Given I shutdown Tails and wait for the computer to power off 10.822
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.141
Then Tails is running version 6.2~testoverlayfs 0.041
And all tps features are active 2.733
And the file system changes introduced in version 6.2~testoverlayfs are present 0.370
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.288
When the network is plugged 0.095
And Tor is ready 16.135
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.539
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.772
Given I shutdown Tails and wait for the computer to power off 4.254
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.069
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.427
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.391
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.059
And Tor is ready 17.927
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 14.220
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.981
After features/support/hooks.rb:326 0.869
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.537
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.823
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.504
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 20.010
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.952
After features/support/hooks.rb:326 0.676
After features/support/hooks.rb:100 0.000