Project Number Date
test_Tails_ISO_devel 3663 27 Jan 2025, 17: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:37.715 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:51.437
Before features/support/hooks.rb:269 0.003
Given a computer 0.544
And I create a 7200 MiB disk named "old" 0.082
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 1:1.170
When I start Tails from USB drive "old" with network unplugged 1:44.300
Then the boot device has safe access rights 3.275
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 10.007
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.377
Before features/support/hooks.rb:269 0.003
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login 1:28.580
Then Tails is running from USB drive "old" 0.420
And I create a persistent partition 33.749
And I take note of which tps features are available 1.908
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 8.628
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.006
Tags: @product
3:0.443
Before features/support/hooks.rb:269 0.003
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.121
Then Tails is running from USB drive "old" 0.396
And all tps features are active 2.449
When I write some files expected to persist 2.318
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.582
And I take note of which tps features are available 0.655
And I shutdown Tails and wait for the computer to power off 4.425
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.641
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.007
Tags: @product
3:3.405
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.198
And I log in to a new session 22.105
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.593
And I plug USB drive "to_upgrade" 3.009
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:56.753
Then the running Tails is installed on USB drive "to_upgrade" 24.229
And I unplug USB drive "to_upgrade" 0.288
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:326 7.027
After features/support/hooks.rb:100 0.000
Tags: @product
2:38.804
Before features/support/hooks.rb:269 0.011
Given a computer 0.444
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:28.455
Then all tps features from the old Tails version are active 1.889
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.631
And the expected persistent files created with the old Tails version are present in the filesystem 1.460
And all persistent directories from the old Tails version have safe access rights 2.534
After features/support/hooks.rb:326 0.846
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
8:7.502
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:5.892
And no SquashFS delta is installed 0.426
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.151
And Tor is ready 19.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.982
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.011
Given I shutdown Tails and wait for the computer to power off 11.986
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.177
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.795
And the file system changes introduced in version 6.2~testoverlayfs are present 0.361
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.333
When the network is plugged 0.136
And Tor is ready 20.419
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.244
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.997
Given I shutdown Tails and wait for the computer to power off 4.792
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.935
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.268
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.374
When the network is plugged 0.072
And Tor is ready 21.721
Then the Upgrader considers the system as up-to-date 0.359
# 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.565
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.175
After features/support/hooks.rb:326 0.875
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
41.744
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 13.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.466
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.121
And Tor is ready 21.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.247
After features/support/hooks.rb:326 0.809
After features/support/hooks.rb:100 0.000