Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 16 27 Apr 2025, 21:07

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:33.822 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:7.053
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.097
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 30.491
When I start Tails from USB drive "old" with network unplugged 1:31.074
Then the boot device has safe access rights 3.112
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:330 3.750
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.808
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:27.253
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 30.815
And I take note of which tps features are available 1.806
Then a Tails persistence partition exists on USB drive "old" 0.793
And I shutdown Tails and wait for the computer to power off 8.599
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.958
Then Tails is running from USB drive "old" 0.793
And all tps features are active 2.119
When I write some files expected to persist 1.825
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 3.589
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 4.334
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.567
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.583
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.747
And I log in to a new session 19.700
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.443
And I plug USB drive "to_upgrade" 2.408
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.422
Then the running Tails is installed on USB drive "to_upgrade" 27.380
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.273
After features/support/hooks.rb:330 1.307
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.108
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 "to_upgrade" with network unplugged and I login with persistence enabled 2:4.587
Then all tps features from the old Tails version are active 1.599
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 4.494
And the expected persistent files created with the old Tails version are present in the filesystem 1.458
And all persistent directories from the old Tails version have safe access rights 2.435
After features/support/hooks.rb:330 0.824
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:48.394
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 11.607
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.400
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.436
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.072
And Tor is ready 21.232
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.515
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.743
Given I shutdown Tails and wait for the computer to power off 11.128
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.714
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.493
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.448
# 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.280
When the network is plugged 0.076
And Tor is ready 18.264
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.058
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.191
Given I shutdown Tails and wait for the computer to power off 4.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.282
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.195
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.070
And Tor is ready 19.167
Then the Upgrader considers the system as up-to-date 0.324
# 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.280
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.742
After features/support/hooks.rb:330 0.811
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.278
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.707
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.468
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.114
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 19.045
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.770
After features/support/hooks.rb:330 1.430
After features/support/hooks.rb:100 0.000