Project Number Date
test_Tails_ISO_stable 5501 07 Mar 2025, 12:59

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:10.470 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.547
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 35.627
When I start Tails from USB drive "old" with network unplugged 1:35.241
Then the boot device has safe access rights 3.363
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.539
After features/support/hooks.rb:100 0.028
Tags: @product
2:12.482
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:28.696
Then Tails is running from USB drive "old" 0.465
And I create a persistent partition 32.111
And I take note of which tps features are available 1.733
Then a Tails persistence partition exists on USB drive "old" 0.905
And I shutdown Tails and wait for the computer to power off 8.365
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.010
Tags: @product
3:10.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.024
Then Tails is running from USB drive "old" 0.410
And all tps features are active 2.575
When I write some files expected to persist 1.957
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 2.787
And I take note of which tps features are available 0.607
And I shutdown Tails and wait for the computer to power off 6.326
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.111
After features/support/hooks.rb:330 0.168
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.968
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.995
And I log in to a new session 19.023
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.858
And I plug USB drive "to_upgrade" 2.534
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.373
Then the running Tails is installed on USB drive "to_upgrade" 24.632
And I unplug USB drive "to_upgrade" 0.260
And I unplug USB drive "__internal" 0.289
After features/support/hooks.rb:330 2.233
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.141
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.047
Then all tps features from the old Tails version are active 1.764
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.717
And the expected persistent files created with the old Tails version are present in the filesystem 1.537
And all persistent directories from the old Tails version have safe access rights 2.485
After features/support/hooks.rb:330 1.249
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
6:32.741
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.240
And no SquashFS delta is installed 0.253
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.483
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.566
When the network is plugged 0.077
And Tor is ready 23.854
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.845
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.504
Given I shutdown Tails and wait for the computer to power off 10.648
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.497
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.342
And the file system changes introduced in version 6.2~testoverlayfs are present 0.349
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.297
When the network is plugged 0.083
And Tor is ready 21.439
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.300
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.659
Given I shutdown Tails and wait for the computer to power off 4.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.706
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.383
And the file system changes introduced in version 6.3~testoverlayfs are present 0.573
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.077
And Tor is ready 17.339
Then the Upgrader considers the system as up-to-date 0.357
# 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.042
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.126
After features/support/hooks.rb:330 0.719
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
1:3.938
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.938
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the signing key used by the Upgrader is outdated 0.120
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 52.685
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.630
After features/support/hooks.rb:330 0.684
After features/support/hooks.rb:100 0.000