Project Number Date
test_Tails_ISO_stable 5526 22 Mar 2025, 12:57

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 19:27.531 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:14.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 32.653
When I start Tails from USB drive "old" with network unplugged 1:36.952
Then the boot device has safe access rights 3.045
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 7.507
After features/support/hooks.rb:100 0.008
Tags: @product
2:8.440
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:25.231
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 31.432
And I take note of which tps features are available 2.085
Then a Tails persistence partition exists on USB drive "old" 0.762
And I shutdown Tails and wait for the computer to power off 8.385
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
3:3.017
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 1.128
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.695
Then Tails is running from USB drive "old" 0.417
And all tps features are active 2.618
When I write some files expected to persist 1.898
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.274
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 2.810
And I take note of which tps features are available 0.704
And I shutdown Tails and wait for the computer to power off 4.385
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.627
After features/support/hooks.rb:330 0.119
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.430
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 without a persistent partition and stopped at Tails Greeter's login screen 10.860
And I log in to a new session 20.088
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.654
And I plug USB drive "to_upgrade" 2.480
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.191
Then the running Tails is installed on USB drive "to_upgrade" 22.758
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 1.941
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.159
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.262
Then all tps features from the old Tails version are active 1.669
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.350
And the expected persistent files created with the old Tails version are present in the filesystem 1.557
And all persistent directories from the old Tails version have safe access rights 2.753
After features/support/hooks.rb:330 1.704
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:27.641
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 with a persistent partition enabled and logged in 11.731
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.379
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.083
And Tor is ready 22.335
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.460
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.601
Given I shutdown Tails and wait for the computer to power off 11.086
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.689
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.144
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.274
When the network is plugged 0.088
And Tor is ready 18.479
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.336
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.127
Given I shutdown Tails and wait for the computer to power off 4.325
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.616
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.169
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.353
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.061
And Tor is ready 18.641
Then the Upgrader considers the system as up-to-date 0.329
# 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.839
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.951
After features/support/hooks.rb:330 1.126
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.929
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 with a persistent partition enabled and logged in 10.046
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.125
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 21.624
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.629
After features/support/hooks.rb:330 0.691
After features/support/hooks.rb:100 0.000