Project Number Date
test_Tails_ISO_devel 3731 10 Mar 2025, 13:05

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:30.299 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:6.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 31.487
When I start Tails from USB drive "old" with network unplugged 1:29.139
Then the boot device has safe access rights 3.406
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 7.557
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.493
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:28.186
Then Tails is running from USB drive "old" 0.378
And I create a persistent partition 32.027
And I take note of which tps features are available 1.430
Then a Tails persistence partition exists on USB drive "old" 0.845
And I shutdown Tails and wait for the computer to power off 8.408
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.008
Tags: @product
3:3.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.253
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.519
Then Tails is running from USB drive "old" 0.649
And all tps features are active 1.978
When I write some files expected to persist 1.829
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.314
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 2.762
And I take note of which tps features are available 0.640
And I shutdown Tails and wait for the computer to power off 6.346
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.317
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.354
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 11.637
And I log in to a new session 18.729
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.712
And I plug USB drive "to_upgrade" 2.526
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.267
Then the running Tails is installed on USB drive "to_upgrade" 22.064
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 2.269
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.929
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.252
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.015
Then all tps features from the old Tails version are active 1.691
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.465
And the expected persistent files created with the old Tails version are present in the filesystem 1.626
And all persistent directories from the old Tails version have safe access rights 2.528
After features/support/hooks.rb:330 1.433
After features/support/hooks.rb:100 0.009
6:35.082
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.195
And no SquashFS delta is installed 0.434
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.438
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.090
And Tor is ready 23.829
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.707
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.738
Given I shutdown Tails and wait for the computer to power off 10.846
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.629
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.221
And the file system changes introduced in version 6.2~testoverlayfs are present 0.353
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.288
When the network is plugged 0.091
And Tor is ready 16.672
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.760
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.290
Given I shutdown Tails and wait for the computer to power off 4.425
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.067
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.286
And the file system changes introduced in version 6.3~testoverlayfs are present 0.571
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.082
And Tor is ready 20.773
Then the Upgrader considers the system as up-to-date 0.288
# 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 14.277
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.887
After features/support/hooks.rb:330 0.789
After features/support/hooks.rb:100 0.022
40.015
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 10.698
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 20.826
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.874
After features/support/hooks.rb:330 0.634
After features/support/hooks.rb:100 0.000