Project Number Date
test_Tails_ISO_stable 5434 30 Jan 2025, 22:13

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:27.317 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:4.256
Before features/support/hooks.rb:269 0.004
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.899
When I start Tails from USB drive "old" with network unplugged 1:29.984
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:326 3.532
After features/support/hooks.rb:100 0.029
Tags: @product
2:9.739
Before features/support/hooks.rb:269 0.005
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login 1:25.388
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 33.067
And I take note of which tps features are available 1.319
Then a Tails persistence partition exists on USB drive "old" 1.115
And I shutdown Tails and wait for the computer to power off 8.245
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.008
Tags: @product
3:7.883
Before features/support/hooks.rb:269 0.003
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.163
Then Tails is running from USB drive "old" 1.135
And all tps features are active 1.920
When I write some files expected to persist 1.703
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.516
And all persistent directories from the old Tails version have safe access rights 3.939
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 4.156
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.454
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.887
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 10.924
And I log in to a new session 19.973
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.536
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.748
Then the running Tails is installed on USB drive "to_upgrade" 24.583
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.474
After features/support/hooks.rb:326 2.261
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.317
Before features/support/hooks.rb:269 0.004
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.524
Then all tps features from the old Tails version are active 1.677
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.526
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.578
After features/support/hooks.rb:326 1.069
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:30.203
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.084
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.166
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.547
When the network is plugged 0.073
And Tor is ready 24.138
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.448
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.760
Given I shutdown Tails and wait for the computer to power off 8.984
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.303
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.386
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
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.295
# 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.311
When the network is plugged 0.071
And Tor is ready 20.068
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.165
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.797
Given I shutdown Tails and wait for the computer to power off 4.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.859
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.150
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.317
When the network is plugged 0.074
And Tor is ready 18.577
Then the Upgrader considers the system as up-to-date 0.335
# 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.855
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.046
After features/support/hooks.rb:326 0.771
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.029
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 10.889
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.608
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 20.888
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.421
After features/support/hooks.rb:326 0.908
After features/support/hooks.rb:100 0.000