Project Number Date
test_Tails_ISO_devel 3445 03 Jul 2024, 12:13

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 17:54.105 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:6.285
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 27.790
When I start Tails from USB drive "old" with network unplugged 1:33.510
Then the boot device has safe access rights 2.782
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:326 7.261
After features/support/hooks.rb:100 0.010
Tags: @product
1:58.744
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:16.764
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 30.826
And I take note of which tps features are available 1.525
Then a Tails persistence partition exists on USB drive "old" 0.832
And I shutdown Tails and wait for the computer to power off 8.304
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.923
Before features/support/hooks.rb:269 0.006
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.472
Then Tails is running from USB drive "old" 0.287
And all tps features are active 2.029
When I write some files expected to persist 1.482
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 2.368
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 4.311
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.752
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.143
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 10.685
And I log in to a new session 16.673
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.313
And I plug USB drive "to_upgrade" 2.314
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.729
Then the running Tails is installed on USB drive "to_upgrade" 14.989
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 6.642
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.309
Before features/support/hooks.rb:269 0.007
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.257
Then all tps features from the old Tails version are active 1.640
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 2.844
And the expected persistent files created with the old Tails version are present in the filesystem 1.321
And all persistent directories from the old Tails version have safe access rights 2.698
After features/support/hooks.rb:326 0.626
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:59.600
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 10.876
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.047
And Tor is ready 20.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.799
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.915
Given I shutdown Tails and wait for the computer to power off 8.434
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.203
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.029
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
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.329
# 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.247
When the network is plugged 0.059
And Tor is ready 18.323
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.854
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.875
Given I shutdown Tails and wait for the computer to power off 4.234
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.688
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.032
And the file system changes introduced in version 6.3~testoverlayfs are present 0.437
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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.041
And Tor is ready 18.588
Then the Upgrader considers the system as up-to-date 0.315
# 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.550
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.920
After features/support/hooks.rb:326 0.666
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
37.098
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 12.406
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.740
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 18.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.794
After features/support/hooks.rb:326 0.831
After features/support/hooks.rb:100 0.000