Project Number Date
test_Tails_ISO_devel 3908 15 Jul 2025, 22:54

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 26:39.776 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
3:38.194
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.246
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.201
And I write an old version of the Tails USB image to disk "old" 53.059
When I start Tails from USB drive "old" with network unplugged 2:39.102
Then the boot device has safe access rights 3.452
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 9.808
After features/support/hooks.rb:100 0.032
Tags: @product
3:21.632
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Given a computer 0.846
And I start Tails from USB drive "old" with network unplugged and I login 2:14.015
Then Tails is running from USB drive "old" 0.571
And I create a persistent partition 51.539
And I take note of which tps features are available 2.688
Then a Tails persistence partition exists on USB drive "old" 1.003
And I shutdown Tails and wait for the computer to power off 10.966
After features/support/hooks.rb:330 0.527
After features/support/hooks.rb:100 0.045
Tags: @product
4:23.649
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Given a computer 0.647
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:27.565
Then Tails is running from USB drive "old" 0.635
And all tps features are active 2.611
When I write some files expected to persist 2.815
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.920
And all persistence configuration files have safe access rights 0.923
And all persistent directories from the old Tails version have safe access rights 4.416
And I take note of which tps features are available 0.621
And I shutdown Tails and wait for the computer to power off 6.659
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.834
After features/support/hooks.rb:330 0.237
After features/support/hooks.rb:100 0.016
Tags: @product
3:1.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.324
And I log in to a new session 23.741
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.585
And I plug USB drive "to_upgrade" 2.499
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.164
Then the running Tails is installed on USB drive "to_upgrade" 37.326
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 0.830
After features/support/hooks.rb:100 0.000
Tags: @product
2:42.722
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.276
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:31.082
Then all tps features from the old Tails version are active 2.567
And Tails is running from USB drive "to_upgrade" 0.445
And the boot device has safe access rights 4.130
And the expected persistent files created with the old Tails version are present in the filesystem 1.488
And all persistent directories from the old Tails version have safe access rights 2.731
After features/support/hooks.rb:330 0.718
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
8:40.122
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.567
And no SquashFS delta is installed 0.317
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.481
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.229
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.568
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.077
And Tor is ready 31.329
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.181
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.863
Given I shutdown Tails and wait for the computer to power off 20.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:35.008
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 3.211
And the file system changes introduced in version 6.2~testoverlayfs are present 0.625
And only the 6.2~testoverlayfs SquashFS delta is installed 0.120
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.647
When the network is plugged 0.110
And Tor is ready 21.851
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.425
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.032
Given I shutdown Tails and wait for the computer to power off 4.734
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.031
Then Tails is running version 6.3~testoverlayfs 0.042
And all tps features are active 2.427
And the file system changes introduced in version 6.3~testoverlayfs are present 0.588
And only the 6.3~testoverlayfs SquashFS delta is installed 0.116
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.462
When the network is plugged 0.077
And Tor is ready 48.786
Then the Upgrader considers the system as up-to-date 0.369
# 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 17.909
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.999
After features/support/hooks.rb:330 0.922
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
52.360
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.252
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.129
And the signing key used by the Upgrader is outdated 0.175
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 29.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.978
After features/support/hooks.rb:330 0.918
After features/support/hooks.rb:100 0.000