Project Number Date
test_Tails_ISO_stable 5466 18 Feb 2025, 12:52

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 22:13.203 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:54.565
Before features/support/hooks.rb:269 0.007
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 1:1.971
When I start Tails from USB drive "old" with network unplugged 1:46.648
Then the boot device has safe access rights 3.562
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 4.112
After features/support/hooks.rb:100 0.021
Tags: @product
2:27.625
Before features/support/hooks.rb:269 0.017
Given a computer 1.190
And I start Tails from USB drive "old" with network unplugged and I login 1:32.745
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 38.214
And I take note of which tps features are available 4.542
Then a Tails persistence partition exists on USB drive "old" 1.693
And I shutdown Tails and wait for the computer to power off 8.856
After features/support/hooks.rb:326 0.299
After features/support/hooks.rb:100 0.007
Tags: @product
3:20.277
Before features/support/hooks.rb:269 0.004
Given a computer 0.715
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:40.511
Then Tails is running from USB drive "old" 0.554
And all tps features are active 2.369
When I write some files expected to persist 1.788
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 3.023
And I take note of which tps features are available 0.646
And I shutdown Tails and wait for the computer to power off 4.549
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.387
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.297
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 20.353
And I log in to a new session 20.869
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.701
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.951
Then the running Tails is installed on USB drive "to_upgrade" 22.507
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:326 2.658
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.979
Before features/support/hooks.rb:269 0.005
Given a computer 0.280
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.761
Then all tps features from the old Tails version are active 1.951
And Tails is running from USB drive "to_upgrade" 0.489
And the boot device has safe access rights 3.374
And the expected persistent files created with the old Tails version are present in the filesystem 1.532
And all persistent directories from the old Tails version have safe access rights 2.588
After features/support/hooks.rb:326 0.960
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:31.023
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 22.617
And no SquashFS delta is installed 0.154
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.374
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.572
When the network is plugged 0.118
And Tor is ready 20.761
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.448
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.896
Given I shutdown Tails and wait for the computer to power off 13.577
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.670
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 5.520
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.271
When the network is plugged 0.088
And Tor is ready 20.013
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.241
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.627
Given I shutdown Tails and wait for the computer to power off 4.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.834
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.670
And the file system changes introduced in version 6.3~testoverlayfs are present 0.618
And only the 6.3~testoverlayfs SquashFS delta is installed 0.127
# 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.385
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.329
When the network is plugged 0.106
And Tor is ready 19.670
Then the Upgrader considers the system as up-to-date 0.350
# 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 16.259
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.137
After features/support/hooks.rb:326 1.170
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
43.434
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 12.898
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.092
But a current signing key is available on our website 0.000
When the network is plugged 0.678
And Tor is ready 23.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.423
After features/support/hooks.rb:326 0.924
After features/support/hooks.rb:100 0.000