Project Number Date
test_Tails_ISO_devel 3520 25 Sep 2024, 12:31

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:54.564 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.268
Before features/support/hooks.rb:269 0.004
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.961
When I start Tails from USB drive "old" with network unplugged 1:29.044
Then the boot device has safe access rights 3.000
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.548
After features/support/hooks.rb:100 0.022
Tags: @product
2:3.316
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:20.160
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 31.975
And I take note of which tps features are available 1.724
Then a Tails persistence partition exists on USB drive "old" 0.726
And I shutdown Tails and wait for the computer to power off 8.209
After features/support/hooks.rb:326 0.216
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.587
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.015
Then Tails is running from USB drive "old" 0.336
And all tps features are active 1.834
When I write some files expected to persist 1.460
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.348
And all persistent directories from the old Tails version have safe access rights 2.149
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 4.368
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.217
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.907
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 29.413
And I log in to a new session 19.629
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.523
And I plug USB drive "to_upgrade" 2.397
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.556
Then the running Tails is installed on USB drive "to_upgrade" 17.930
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:326 7.966
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.989
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.266
Then all tps features from the old Tails version are active 1.568
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 2.931
And the expected persistent files created with the old Tails version are present in the filesystem 1.445
And all persistent directories from the old Tails version have safe access rights 2.304
After features/support/hooks.rb:326 0.875
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:22.152
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.596
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.427
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.064
And Tor is ready 20.150
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.454
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.512
Given I shutdown Tails and wait for the computer to power off 8.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.335
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.155
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.259
When the network is plugged 0.101
And Tor is ready 19.313
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.019
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.982
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.092
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.894
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.091
And Tor is ready 15.338
Then the Upgrader considers the system as up-to-date 10.865
# 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.072
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.003
After features/support/hooks.rb:326 0.847
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
40.341
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 15.425
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.824
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 17.929
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.582
After features/support/hooks.rb:326 0.797
After features/support/hooks.rb:100 0.000