Project Number Date
test_Tails_ISO_stable 5322 09 Dec 2024, 08:38

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 19:21.181 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:19.056
Before features/support/hooks.rb:269 0.004
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.414
When I start Tails from USB drive "old" with network unplugged 1:44.390
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 3.531
After features/support/hooks.rb:100 0.022
Tags: @product
2:10.569
Before features/support/hooks.rb:269 0.006
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:26.610
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 32.411
And I take note of which tps features are available 1.628
Then a Tails persistence partition exists on USB drive "old" 0.863
And I shutdown Tails and wait for the computer to power off 8.544
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.011
Tags: @product
2:55.199
Before features/support/hooks.rb:269 0.007
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.588
Then Tails is running from USB drive "old" 1.450
And all tps features are active 2.209
When I write some files expected to persist 1.819
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.560
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 3.618
And I take note of which tps features are available 0.487
And I shutdown Tails and wait for the computer to power off 4.318
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.464
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.769
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.208
And I log in to a new session 21.213
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.721
And I plug USB drive "to_upgrade" 2.431
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.097
Then the running Tails is installed on USB drive "to_upgrade" 21.695
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 3.470
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.814
Before features/support/hooks.rb:269 0.007
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.817
Then all tps features from the old Tails version are active 1.753
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.306
And the expected persistent files created with the old Tails version are present in the filesystem 1.476
And all persistent directories from the old Tails version have safe access rights 2.976
After features/support/hooks.rb:326 1.033
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:31.590
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 13.265
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.538
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.074
And Tor is ready 20.757
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.512
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.148
Given I shutdown Tails and wait for the computer to power off 10.906
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.030
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.202
And the file system changes introduced in version 6.2~testoverlayfs are present 0.426
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.432
# 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.360
When the network is plugged 0.073
And Tor is ready 19.214
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.509
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.625
Given I shutdown Tails and wait for the computer to power off 4.320
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.509
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.255
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.068
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.091
And Tor is ready 18.734
Then the Upgrader considers the system as up-to-date 0.323
# 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 15.941
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.101
After features/support/hooks.rb:326 0.823
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.181
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.498
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.479
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 1.685
But a current signing key is available on our website 0.000
When the network is plugged 0.555
And Tor is ready 16.321
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.571
After features/support/hooks.rb:326 0.739
After features/support/hooks.rb:100 0.000