Project Number Date
test_Tails_ISO_stable 5436 01 Feb 2025, 08:36

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:16.384 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
1:59.098
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.977
When I start Tails from USB drive "old" with network unplugged 1:24.999
Then the boot device has safe access rights 2.843
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.495
After features/support/hooks.rb:100 0.008
Tags: @product
2:0.444
Before features/support/hooks.rb:269 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:18.483
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 30.973
And I take note of which tps features are available 1.405
Then a Tails persistence partition exists on USB drive "old" 0.731
And I shutdown Tails and wait for the computer to power off 8.327
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.265
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:11.639
Then Tails is running from USB drive "old" 0.298
And all tps features are active 1.817
When I write some files expected to persist 1.753
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.514
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 4.247
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.743
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.233
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 9.716
And I log in to a new session 18.492
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.562
And I plug USB drive "to_upgrade" 2.450
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.341
Then the running Tails is installed on USB drive "to_upgrade" 18.244
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 2.367
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.129
Before features/support/hooks.rb:269 0.006
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.936
Then all tps features from the old Tails version are active 1.603
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.189
And the expected persistent files created with the old Tails version are present in the filesystem 1.375
And all persistent directories from the old Tails version have safe access rights 2.507
After features/support/hooks.rb:326 0.618
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:20.325
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 16.946
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.077
And Tor is ready 23.463
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.485
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.847
Given I shutdown Tails and wait for the computer to power off 8.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.129
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.076
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.518
# 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.438
When the network is plugged 0.066
And Tor is ready 18.395
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.256
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.386
Given I shutdown Tails and wait for the computer to power off 4.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.106
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.947
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.380
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.090
And Tor is ready 18.758
Then the Upgrader considers the system as up-to-date 0.355
# 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.593
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.933
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.886
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 10.279
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
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.062
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 18.582
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.515
After features/support/hooks.rb:326 0.643
After features/support/hooks.rb:100 0.000