Project Number Date
test_Tails_ISO_stable 5066 04 Sep 2024, 08:34

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 20:0.484 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:5.605
Before features/support/hooks.rb:269 0.002
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 30.618
When I start Tails from USB drive "old" with network unplugged 1:29.646
Then the boot device has safe access rights 2.967
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.346
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.498
After features/support/hooks.rb:100 0.029
Tags: @product
2:13.931
Before features/support/hooks.rb:269 0.002
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:32.339
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 30.701
And I take note of which tps features are available 1.396
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.179
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.006
Tags: @product
2:51.945
Before features/support/hooks.rb:269 0.002
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.784
Then Tails is running from USB drive "old" 0.358
And all tps features are active 1.915
When I write some files expected to persist 1.885
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.438
And all persistent directories from the old Tails version have safe access rights 2.829
And I take note of which tps features are available 0.413
And I shutdown Tails and wait for the computer to power off 4.579
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.334
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.007
Tags: @product
2:37.997
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.673
And I log in to a new session 19.985
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.348
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.600
Then the running Tails is installed on USB drive "to_upgrade" 22.379
And I unplug USB drive "to_upgrade" 0.269
And I unplug USB drive "__internal" 0.261
After features/support/hooks.rb:326 2.163
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.239
Before features/support/hooks.rb:269 0.002
Given a computer 0.159
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.328
Then all tps features from the old Tails version are active 1.722
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.427
And the expected persistent files created with the old Tails version are present in the filesystem 1.627
And all persistent directories from the old Tails version have safe access rights 2.647
After features/support/hooks.rb:326 0.644
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
6:55.146
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.103
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.374
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.659
When the network is plugged 0.101
And Tor is ready 18.807
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.707
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.237
Given I shutdown Tails and wait for the computer to power off 11.352
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.783
Then Tails is running version 6.2~testoverlayfs 0.082
And all tps features are active 2.149
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.314
When the network is plugged 0.086
And Tor is ready 16.620
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.423
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.554
Given I shutdown Tails and wait for the computer to power off 4.509
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.450
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 1.974
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.370
When the network is plugged 0.059
And Tor is ready 17.030
Then the Upgrader considers the system as up-to-date 10.903
# 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.156
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.014
After features/support/hooks.rb:326 0.699
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
1:1.618
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.568
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 1.013
But a current signing key is available on our website 0.000
When the network is plugged 0.152
And Tor is ready 49.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.600
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.000