Project Number Date
test_Tails_ISO_stable 5382 09 Jan 2025, 08:47

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:1.043 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.217
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.741
When I start Tails from USB drive "old" with network unplugged 1:31.310
Then the boot device has safe access rights 2.939
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.521
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.102
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:27.090
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 31.090
And I take note of which tps features are available 1.474
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 8.211
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.229
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.687
Then Tails is running from USB drive "old" 0.404
And all tps features are active 1.901
When I write some files expected to persist 1.936
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.413
And I take note of which tps features are available 0.655
And I shutdown Tails and wait for the computer to power off 4.403
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.981
After features/support/hooks.rb:326 0.094
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.089
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 9.737
And I log in to a new session 16.894
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.446
And I plug USB drive "to_upgrade" 2.376
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.376
Then the running Tails is installed on USB drive "to_upgrade" 16.806
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:326 3.537
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.289
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.097
Then all tps features from the old Tails version are active 1.645
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.060
And the expected persistent files created with the old Tails version are present in the filesystem 1.637
And all persistent directories from the old Tails version have safe access rights 2.328
After features/support/hooks.rb:326 1.252
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:34.570
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 11.627
And no SquashFS delta is installed 0.236
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.064
And Tor is ready 20.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.573
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.473
Given I shutdown Tails and wait for the computer to power off 1:11.881
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.022
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.125
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.259
# 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.243
When the network is plugged 0.076
And Tor is ready 44.644
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.569
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.678
Given I shutdown Tails and wait for the computer to power off 4.634
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.472
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.293
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.088
And Tor is ready 19.340
Then the Upgrader considers the system as up-to-date 0.292
# 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.073
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.244
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
35.544
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 9.859
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 20.331
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.810
After features/support/hooks.rb:326 0.634
After features/support/hooks.rb:100 0.000