Project Number Date
test_Tails_ISO_stable 5163 09 Oct 2024, 15:51

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:57.634 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:13.141
Before features/support/hooks.rb:269 0.011
Given a computer 0.255
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 30.639
When I start Tails from USB drive "old" with network unplugged 1:36.233
Then the boot device has safe access rights 3.562
And Tails is running from USB drive "old" 0.483
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.373
And I unplug USB drive "old" 0.274
After features/support/hooks.rb:326 7.128
After features/support/hooks.rb:100 0.012
Tags: @product
2:10.334
Before features/support/hooks.rb:269 0.010
Given a computer 0.261
And I start Tails from USB drive "old" with network unplugged and I login 1:25.290
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 35.102
And I take note of which tps features are available 1.865
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 6.578
After features/support/hooks.rb:326 0.220
After features/support/hooks.rb:100 0.009
Tags: @product
3:1.721
Before features/support/hooks.rb:269 0.005
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.800
Then Tails is running from USB drive "old" 0.357
And all tps features are active 3.033
When I write some files expected to persist 1.969
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.285
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 2.671
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 4.300
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.082
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.347
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.039
And I log in to a new session 20.732
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.100
And I plug USB drive "to_upgrade" 2.506
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.097
Then the running Tails is installed on USB drive "to_upgrade" 22.469
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 2.420
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.981
Before features/support/hooks.rb:269 0.006
Given a computer 0.306
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.309
Then all tps features from the old Tails version are active 2.081
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.681
And the expected persistent files created with the old Tails version are present in the filesystem 1.534
And all persistent directories from the old Tails version have safe access rights 2.711
After features/support/hooks.rb:326 0.812
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:57.353
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 12.933
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.368
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.081
And Tor is ready 21.168
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.106
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.003
Given I shutdown Tails and wait for the computer to power off 13.205
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.181
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.655
And the file system changes introduced in version 6.2~testoverlayfs are present 0.447
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.378
# 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.655
When the network is plugged 0.117
And Tor is ready 19.994
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.898
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.692
Given I shutdown Tails and wait for the computer to power off 4.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.009
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.007
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.129
And Tor is ready 17.226
Then the Upgrader considers the system as up-to-date 10.848
# 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.636
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.944
After features/support/hooks.rb:326 0.788
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
39.754
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.984
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.823
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 21.175
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.286
After features/support/hooks.rb:326 0.887
After features/support/hooks.rb:100 0.000