Project Number Date
test_Tails_ISO_stable 5508 11 Mar 2025, 19:31

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 20:14.650 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:16.791
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 31.267
When I start Tails from USB drive "old" with network unplugged 1:39.945
Then the boot device has safe access rights 3.219
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:330 3.543
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.716
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:29.073
Then Tails is running from USB drive "old" 0.410
And I create a persistent partition 34.278
And I take note of which tps features are available 1.569
Then a Tails persistence partition exists on USB drive "old" 0.859
And I shutdown Tails and wait for the computer to power off 8.342
After features/support/hooks.rb:330 0.119
After features/support/hooks.rb:100 0.008
Tags: @product
3:9.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.035
Then Tails is running from USB drive "old" 0.856
And all tps features are active 3.724
When I write some files expected to persist 2.925
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 3.115
And I take note of which tps features are available 0.830
And I shutdown Tails and wait for the computer to power off 4.079
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.000
After features/support/hooks.rb:330 0.105
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.657
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.992
And I log in to a new session 20.448
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.474
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.466
Then the running Tails is installed on USB drive "to_upgrade" 25.324
And I unplug USB drive "to_upgrade" 0.246
And I unplug USB drive "__internal" 0.261
After features/support/hooks.rb:330 6.659
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.337
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.201
Then all tps features from the old Tails version are active 1.724
And Tails is running from USB drive "to_upgrade" 0.373
And the boot device has safe access rights 3.724
And the expected persistent files created with the old Tails version are present in the filesystem 1.492
And all persistent directories from the old Tails version have safe access rights 2.600
After features/support/hooks.rb:330 1.371
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:0.467
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 12.742
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.118
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.531
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.611
When the network is plugged 0.077
And Tor is ready 19.944
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.762
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.637
Given I shutdown Tails and wait for the computer to power off 11.477
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.942
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.313
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.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.272
# 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.302
When the network is plugged 0.090
And Tor is ready 17.368
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.672
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.601
Given I shutdown Tails and wait for the computer to power off 4.529
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.832
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.215
And the file system changes introduced in version 6.3~testoverlayfs are present 0.674
And only the 6.3~testoverlayfs SquashFS delta is installed 0.115
# 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.565
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.499
When the network is plugged 0.084
And Tor is ready 18.000
Then the Upgrader considers the system as up-to-date 0.339
# 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.011
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.208
After features/support/hooks.rb:330 0.833
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.257
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 10.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.576
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 20.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.112
After features/support/hooks.rb:330 0.767
After features/support/hooks.rb:100 0.000