Project Number Date
test_Tails_ISO_devel 3517 22 Sep 2024, 12:35

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:9.143 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.735
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 29.396
When I start Tails from USB drive "old" with network unplugged 1:23.916
Then the boot device has safe access rights 3.149
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 7.307
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.176
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:29.393
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 31.630
And I take note of which tps features are available 1.467
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.373
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.009
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.384
Then Tails is running from USB drive "old" 0.347
And all tps features are active 2.095
When I write some files expected to persist 1.685
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.274
And all persistence configuration files have safe access rights 0.633
And all persistent directories from the old Tails version have safe access rights 2.357
And I take note of which tps features are available 0.495
And I shutdown Tails and wait for the computer to power off 4.337
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.208
After features/support/hooks.rb:326 0.109
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.793
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.995
And I log in to a new session 19.181
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.592
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.168
Then the running Tails is installed on USB drive "to_upgrade" 19.946
And I unplug USB drive "to_upgrade" 0.289
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 2.364
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.203
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.166
Then all tps features from the old Tails version are active 1.564
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 3.168
And the expected persistent files created with the old Tails version are present in the filesystem 1.557
And all persistent directories from the old Tails version have safe access rights 2.262
After features/support/hooks.rb:326 0.630
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:6.719
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 11.586
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.412
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.075
And Tor is ready 16.707
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.953
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.965
Given I shutdown Tails and wait for the computer to power off 10.662
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.141
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.111
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.276
# 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.286
When the network is plugged 0.081
And Tor is ready 17.645
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.420
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.881
Given I shutdown Tails and wait for the computer to power off 4.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.494
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.946
And the file system changes introduced in version 6.3~testoverlayfs are present 0.449
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.276
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.068
And Tor is ready 18.206
Then the Upgrader considers the system as up-to-date 0.321
# 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.892
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.949
After features/support/hooks.rb:326 0.760
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
34.505
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 11.394
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.884
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 15.324
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.507
After features/support/hooks.rb:326 0.967
After features/support/hooks.rb:100 0.000