Project Number Date
test_Tails_ISO_devel 3483 17 Aug 2024, 12:32

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:39.522 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
1:58.981
Before features/support/hooks.rb:269 0.008
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.204
When I start Tails from USB drive "old" with network unplugged 1:23.492
Then the boot device has safe access rights 2.978
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.565
After features/support/hooks.rb:100 0.011
Tags: @product
2:7.139
Before features/support/hooks.rb:269 0.008
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:21.012
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 35.102
And I take note of which tps features are available 1.301
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.409
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.011
Tags: @product
2:51.033
Before features/support/hooks.rb:269 0.008
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.854
Then Tails is running from USB drive "old" 0.329
And all tps features are active 2.041
When I write some files expected to persist 1.723
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.556
And I take note of which tps features are available 0.473
And I shutdown Tails and wait for the computer to power off 4.285
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.961
After features/support/hooks.rb:326 0.105
After features/support/hooks.rb:100 0.014
Tags: @product
2:26.063
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.909
And I log in to a new session 18.218
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.527
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.053
Then the running Tails is installed on USB drive "to_upgrade" 18.489
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.240
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.233
Before features/support/hooks.rb:269 0.008
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.158
Then all tps features from the old Tails version are active 1.640
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 3.091
And the expected persistent files created with the old Tails version are present in the filesystem 1.642
And all persistent directories from the old Tails version have safe access rights 2.227
After features/support/hooks.rb:326 0.859
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
6:32.558
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 11.363
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.061
And Tor is ready 21.146
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.650
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.292
Given I shutdown Tails and wait for the computer to power off 8.994
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.516
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 2.363
And the file system changes introduced in version 6.2~testoverlayfs are present 0.410
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.300
When the network is plugged 0.074
And Tor is ready 21.167
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.902
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.874
Given I shutdown Tails and wait for the computer to power off 4.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.933
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.926
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.080
And Tor is ready 17.148
Then the Upgrader considers the system as up-to-date 0.362
# 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.608
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.125
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
32.514
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 10.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 1.277
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 15.493
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.261
After features/support/hooks.rb:326 0.690
After features/support/hooks.rb:100 0.000