Project Number Date
test_Tails_ISO_20668-unblock-20-time.sh 3 20 Nov 2024, 19:45

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 23:0.734 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
3:14.158
Before features/support/hooks.rb:269 0.012
Given a computer 0.306
And I create a 7200 MiB disk named "old" 0.111
And I plug USB drive "old" 1.082
And I write an old version of the Tails USB image to disk "old" 1:30.162
When I start Tails from USB drive "old" with network unplugged 1:38.151
Then the boot device has safe access rights 3.301
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 7.264
After features/support/hooks.rb:100 0.015
Tags: @product
2:19.526
Before features/support/hooks.rb:269 0.010
Given a computer 0.285
And I start Tails from USB drive "old" with network unplugged and I login 1:27.845
Then Tails is running from USB drive "old" 0.411
And I create a persistent partition 39.087
And I take note of which tps features are available 2.180
Then a Tails persistence partition exists on USB drive "old" 0.858
And I shutdown Tails and wait for the computer to power off 8.857
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.993
Before features/support/hooks.rb:269 0.005
Given a computer 0.284
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.092
Then Tails is running from USB drive "old" 0.398
And all tps features are active 2.730
When I write some files expected to persist 1.784
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.509
And all persistent directories from the old Tails version have safe access rights 2.906
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 4.554
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.017
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.030
Tags: @product
2:49.112
Before features/support/hooks.rb:269 0.014
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.769
And I log in to a new session 21.444
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.922
And I plug USB drive "to_upgrade" 2.576
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.166
Then the running Tails is installed on USB drive "to_upgrade" 23.763
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:326 5.292
After features/support/hooks.rb:100 0.000
Tags: @product
2:38.940
Before features/support/hooks.rb:269 0.008
Given a computer 0.254
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.958
Then all tps features from the old Tails version are active 3.994
And Tails is running from USB drive "to_upgrade" 0.436
And the boot device has safe access rights 3.680
And the expected persistent files created with the old Tails version are present in the filesystem 1.614
And all persistent directories from the old Tails version have safe access rights 3.002
After features/support/hooks.rb:326 1.024
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:10.503
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 27.259
And no SquashFS delta is installed 0.340
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.526
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.583
When the network is plugged 0.090
And Tor is ready 25.060
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.131
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.304
Given I shutdown Tails and wait for the computer to power off 13.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:46.436
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.769
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.395
When the network is plugged 0.751
And Tor is ready 21.407
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.465
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.348
Given I shutdown Tails and wait for the computer to power off 4.636
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.009
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 2.350
And the file system changes introduced in version 6.3~testoverlayfs are present 0.550
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.431
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.092
And Tor is ready 19.036
Then the Upgrader considers the system as up-to-date 10.881
# 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 16.556
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.070
After features/support/hooks.rb:326 0.859
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
43.500
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.521
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 1.033
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 23.937
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.471
After features/support/hooks.rb:326 0.702
After features/support/hooks.rb:100 0.000