Project Number Date
test_Tails_ISO_stable 4922 09 Jul 2024, 12:54

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:46.728 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.402
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.094
And I plug USB drive "old" 1.408
And I write an old version of the Tails USB image to disk "old" 31.630
When I start Tails from USB drive "old" with network unplugged 1:29.088
Then the boot device has safe access rights 3.074
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.534
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.175
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:24.404
Then Tails is running from USB drive "old" 0.286
And I create a persistent partition 31.566
And I take note of which tps features are available 1.452
Then a Tails persistence partition exists on USB drive "old" 0.824
And I shutdown Tails and wait for the computer to power off 8.429
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.773
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.825
Then Tails is running from USB drive "old" 0.301
And all tps features are active 1.986
When I write some files expected to persist 1.944
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.327
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 4.338
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.832
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.889
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 11.221
And I log in to a new session 18.822
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.719
And I plug USB drive "to_upgrade" 2.374
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.243
Then the running Tails is installed on USB drive "to_upgrade" 22.098
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:326 6.797
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.844
Before features/support/hooks.rb:269 0.007
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.337
Then all tps features from the old Tails version are active 1.738
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 3.254
And the expected persistent files created with the old Tails version are present in the filesystem 1.543
And all persistent directories from the old Tails version have safe access rights 2.455
After features/support/hooks.rb:326 0.932
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:18.092
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.454
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.401
When the network is plugged 0.075
And Tor is ready 21.141
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.019
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.413
Given I shutdown Tails and wait for the computer to power off 8.591
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.046
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.190
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.288
When the network is plugged 0.036
And Tor is ready 16.089
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.786
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.509
Given I shutdown Tails and wait for the computer to power off 4.417
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.589
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.944
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.055
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.045
And Tor is ready 16.286
Then the Upgrader considers the system as up-to-date 10.715
# 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 13.531
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.895
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
33.549
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 10.035
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.782
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 17.330
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.017
After features/support/hooks.rb:326 0.635
After features/support/hooks.rb:100 0.000