Project Number Date
test_Tails_ISO_devel 3696 17 Feb 2025, 13:06

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:29.526 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:17.941
Before features/support/hooks.rb:269 0.004
Given a computer 0.251
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 34.056
When I start Tails from USB drive "old" with network unplugged 1:38.257
Then the boot device has safe access rights 3.225
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 0.856
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.597
Before features/support/hooks.rb:269 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:28.002
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 31.214
And I take note of which tps features are available 1.536
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.480
After features/support/hooks.rb:326 0.265
After features/support/hooks.rb:100 0.009
Tags: @product
3:4.174
Before features/support/hooks.rb:269 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.323
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.263
When I write some files expected to persist 1.876
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 3.051
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 4.475
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.401
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.800
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 10.574
And I log in to a new session 18.953
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.603
And I plug USB drive "to_upgrade" 2.399
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.980
Then the running Tails is installed on USB drive "to_upgrade" 18.607
And I unplug USB drive "to_upgrade" 0.316
And I unplug USB drive "__internal" 0.363
After features/support/hooks.rb:326 3.575
After features/support/hooks.rb:100 0.000
Tags: @product
2:43.415
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:30.853
Then all tps features from the old Tails version are active 2.114
And Tails is running from USB drive "to_upgrade" 0.432
And the boot device has safe access rights 4.386
And the expected persistent files created with the old Tails version are present in the filesystem 1.994
And all persistent directories from the old Tails version have safe access rights 3.440
After features/support/hooks.rb:326 1.159
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:3.945
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 31.666
And no SquashFS delta is installed 0.145
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.507
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.450
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.628
When the network is plugged 0.116
And Tor is ready 21.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.862
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.593
Given I shutdown Tails and wait for the computer to power off 8.557
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.546
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.798
And the file system changes introduced in version 6.2~testoverlayfs are present 0.444
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.345
When the network is plugged 0.086
And Tor is ready 19.170
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.723
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.929
Given I shutdown Tails and wait for the computer to power off 6.751
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.338
Then Tails is running version 6.3~testoverlayfs 0.049
And all tps features are active 2.625
And the file system changes introduced in version 6.3~testoverlayfs are present 0.766
And only the 6.3~testoverlayfs SquashFS delta is installed 0.152
# 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.515
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.542
When the network is plugged 0.121
And Tor is ready 20.182
Then the Upgrader considers the system as up-to-date 0.332
# 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 18.781
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.146
After features/support/hooks.rb:326 0.974
After features/support/hooks.rb:100 0.040
Tags: @product @automatic_upgrade
42.652
Before features/support/hooks.rb:269 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.924
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 21.602
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.451
After features/support/hooks.rb:326 0.829
After features/support/hooks.rb:100 0.000