Project Number Date
test_Tails_ISO_stable 5283 21 Nov 2024, 17:21

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:20.456 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:1.337
Before features/support/hooks.rb:269 0.006
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.994
When I start Tails from USB drive "old" with network unplugged 1:23.737
Then the boot device has safe access rights 3.303
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:326 3.761
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.639
Before features/support/hooks.rb:269 0.004
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:26.655
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 32.574
And I take note of which tps features are available 1.468
Then a Tails persistence partition exists on USB drive "old" 0.878
And I shutdown Tails and wait for the computer to power off 8.527
After features/support/hooks.rb:326 0.227
After features/support/hooks.rb:100 0.013
Tags: @product
2:50.914
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:13.672
Then Tails is running from USB drive "old" 0.528
And all tps features are active 1.799
When I write some files expected to persist 1.752
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.363
And all persistent directories from the old Tails version have safe access rights 3.173
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 4.263
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.450
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.354
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 11.703
And I log in to a new session 22.637
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.131
And I plug USB drive "to_upgrade" 2.490
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.060
Then the running Tails is installed on USB drive "to_upgrade" 22.921
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:326 2.504
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.270
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.410
Then all tps features from the old Tails version are active 2.165
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.314
And the expected persistent files created with the old Tails version are present in the filesystem 1.404
And all persistent directories from the old Tails version have safe access rights 2.425
After features/support/hooks.rb:326 1.149
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:43.176
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.706
And no SquashFS delta is installed 0.483
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.571
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.174
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.501
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.688
When the network is plugged 0.079
And Tor is ready 23.200
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.899
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.728
Given I shutdown Tails and wait for the computer to power off 11.089
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.349
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.707
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.306
When the network is plugged 0.074
And Tor is ready 16.982
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.662
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.440
Given I shutdown Tails and wait for the computer to power off 4.582
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.497
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.964
And the file system changes introduced in version 6.3~testoverlayfs are present 0.586
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.630
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.344
When the network is plugged 0.083
And Tor is ready 16.896
Then the Upgrader considers the system as up-to-date 0.339
# 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.676
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.083
After features/support/hooks.rb:326 0.842
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.762
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.358
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the signing key used by the Upgrader is outdated 0.970
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 18.406
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.540
After features/support/hooks.rb:326 0.709
After features/support/hooks.rb:100 0.000