Project Number Date
test_Tails_ISO_stable 5551 03 Apr 2025, 17:23

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 21:0.401 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:11.205
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.933
When I start Tails from USB drive "old" with network unplugged 1:34.087
Then the boot device has safe access rights 3.576
And Tails is running from USB drive "old" 0.401
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.343
After features/support/hooks.rb:330 3.696
After features/support/hooks.rb:100 0.013
Tags: @product
2:10.265
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:27.302
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 31.660
And I take note of which tps features are available 1.504
Then a Tails persistence partition exists on USB drive "old" 0.835
And I shutdown Tails and wait for the computer to power off 8.410
After features/support/hooks.rb:330 0.184
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.743
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.047
Then Tails is running from USB drive "old" 1.450
And all tps features are active 2.013
When I write some files expected to persist 1.959
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 4.925
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 6.605
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.404
After features/support/hooks.rb:330 0.139
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.605
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.595
And I log in to a new session 22.550
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.038
And I plug USB drive "to_upgrade" 2.495
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.898
Then the running Tails is installed on USB drive "to_upgrade" 24.115
And I unplug USB drive "to_upgrade" 0.390
And I unplug USB drive "__internal" 0.520
After features/support/hooks.rb:330 4.514
After features/support/hooks.rb:100 0.000
Tags: @product
2:36.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.261
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:26.891
Then all tps features from the old Tails version are active 1.837
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.629
And the expected persistent files created with the old Tails version are present in the filesystem 1.611
And all persistent directories from the old Tails version have safe access rights 2.405
After features/support/hooks.rb:330 1.528
After features/support/hooks.rb:100 0.009
7:34.628
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 35.687
And no SquashFS delta is installed 0.290
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.569
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.127
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.459
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.089
And Tor is ready 50.141
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.695
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.967
Given I shutdown Tails and wait for the computer to power off 8.792
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.426
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.336
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.326
When the network is plugged 0.069
And Tor is ready 21.401
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.909
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.876
Given I shutdown Tails and wait for the computer to power off 4.328
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.175
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.982
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.072
And Tor is ready 20.047
Then the Upgrader considers the system as up-to-date 0.367
# 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.506
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.528
After features/support/hooks.rb:330 0.786
After features/support/hooks.rb:100 0.013
37.978
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.331
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.168
But a current signing key is available on our website 0.000
When the network is plugged 0.129
And Tor is ready 18.753
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.094
After features/support/hooks.rb:330 0.744
After features/support/hooks.rb:100 0.000