Project Number Date
test_Tails_ISO_20267-webtunnel 5 15 Jul 2025, 00:44

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 25:48.631 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:45.731
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.298
And I create a 7200 MiB disk named "old" 0.078
And I plug USB drive "old" 1.091
And I write an old version of the Tails USB image to disk "old" 42.434
When I start Tails from USB drive "old" with network unplugged 1:57.187
Then the boot device has safe access rights 3.560
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 3.906
After features/support/hooks.rb:100 0.010
Tags: @product
3:5.635
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 "old" with network unplugged and I login 2:2.753
Then Tails is running from USB drive "old" 3.619
And I create a persistent partition 44.760
And I take note of which tps features are available 2.929
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 10.564
After features/support/hooks.rb:330 0.837
After features/support/hooks.rb:100 0.045
Tags: @product
4:1.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.407
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:0.970
Then Tails is running from USB drive "old" 2.251
And all tps features are active 2.933
When I write some files expected to persist 1.880
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.466
And all persistent directories from the old Tails version have safe access rights 3.166
And I take note of which tps features are available 0.621
And I shutdown Tails and wait for the computer to power off 9.823
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 38.955
After features/support/hooks.rb:330 0.277
After features/support/hooks.rb:100 0.020
Tags: @product
3:19.470
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.271
And I log in to a new session 28.233
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.172
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.766
Then the running Tails is installed on USB drive "to_upgrade" 42.416
And I unplug USB drive "to_upgrade" 0.814
And I unplug USB drive "__internal" 0.379
After features/support/hooks.rb:330 4.499
After features/support/hooks.rb:100 0.000
Tags: @product
2:47.550
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:35.493
Then all tps features from the old Tails version are active 2.907
And Tails is running from USB drive "to_upgrade" 0.541
And the boot device has safe access rights 3.649
And the expected persistent files created with the old Tails version are present in the filesystem 1.592
And all persistent directories from the old Tails version have safe access rights 3.150
After features/support/hooks.rb:330 4.630
After features/support/hooks.rb:100 0.056
8:56.865
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.038
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.262
And no SquashFS delta is installed 0.475
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.815
And the file system changes introduced in version 6.3~testoverlayfs are not present 4.618
When the network is plugged 0.442
And Tor is ready 27.628
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.038
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.416
Given I shutdown Tails and wait for the computer to power off 14.740
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:51.020
Then Tails is running version 6.2~testoverlayfs 0.103
And all tps features are active 3.818
And the file system changes introduced in version 6.2~testoverlayfs are present 0.515
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.570
When the network is plugged 0.085
And Tor is ready 22.978
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 16.055
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.818
Given I shutdown Tails and wait for the computer to power off 10.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:41.748
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.094
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.389
When the network is plugged 0.103
And Tor is ready 22.369
Then the Upgrader considers the system as up-to-date 0.343
# 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 20.283
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.984
After features/support/hooks.rb:330 6.273
After features/support/hooks.rb:100 0.060
51.650
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.931
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.996
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.395
And the signing key used by the Upgrader is outdated 0.635
But a current signing key is available on our website 0.000
When the network is plugged 0.986
And Tor is ready 26.617
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.087
After features/support/hooks.rb:330 0.969
After features/support/hooks.rb:100 0.000