Project Number Date
test_Tails_ISO_devel 3460 12 Jul 2024, 12:23

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:19.672 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:28.030
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.410
When I start Tails from USB drive "old" with network unplugged 1:53.601
Then the boot device has safe access rights 2.821
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.281
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 3.504
After features/support/hooks.rb:100 0.010
Tags: @product
2:1.427
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:19.690
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 30.378
And I take note of which tps features are available 1.776
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 8.267
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.010
Tags: @product
2:44.352
Before features/support/hooks.rb:269 0.007
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.746
Then Tails is running from USB drive "old" 0.303
And all tps features are active 2.058
When I write some files expected to persist 1.762
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 2.292
And I take note of which tps features are available 0.376
And I shutdown Tails and wait for the computer to power off 4.346
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.599
After features/support/hooks.rb:326 0.106
After features/support/hooks.rb:100 0.010
Tags: @product
2:24.041
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 11.200
And I log in to a new session 16.929
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.380
And I plug USB drive "to_upgrade" 2.391
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.197
Then the running Tails is installed on USB drive "to_upgrade" 15.557
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 2.423
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.813
Before features/support/hooks.rb:269 0.008
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.152
Then all tps features from the old Tails version are active 1.473
And Tails is running from USB drive "to_upgrade" 0.292
And the boot device has safe access rights 3.162
And the expected persistent files created with the old Tails version are present in the filesystem 1.310
And all persistent directories from the old Tails version have safe access rights 2.233
After features/support/hooks.rb:326 0.757
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:3.200
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.740
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.046
And Tor is ready 18.047
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.164
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.876
Given I shutdown Tails and wait for the computer to power off 8.329
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.256
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.320
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.237
When the network is plugged 0.039
And Tor is ready 15.984
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.312
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.676
Given I shutdown Tails and wait for the computer to power off 4.245
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.970
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.905
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.062
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.049
And Tor is ready 18.129
Then the Upgrader considers the system as up-to-date 0.305
# 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 13.488
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.046
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
34.806
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.801
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
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.779
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 18.892
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.878
After features/support/hooks.rb:326 0.603
After features/support/hooks.rb:100 0.000