Project Number Date
test_Tails_ISO_devel 3857 07 Jun 2025, 12:28

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 18:48.163 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:3.942
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.728
When I start Tails from USB drive "old" with network unplugged 1:27.983
Then the boot device has safe access rights 2.946
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:330 6.900
After features/support/hooks.rb:100 0.010
Tags: @product
2:4.456
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:21.913
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 31.443
And I take note of which tps features are available 1.585
Then a Tails persistence partition exists on USB drive "old" 0.780
And I shutdown Tails and wait for the computer to power off 8.234
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.890
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.869
Then Tails is running from USB drive "old" 0.306
And all tps features are active 1.764
When I write some files expected to persist 1.543
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 2.222
And I take note of which tps features are available 0.378
And I shutdown Tails and wait for the computer to power off 4.277
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.792
After features/support/hooks.rb:330 0.108
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.616
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.544
And I log in to a new session 18.137
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.559
And I plug USB drive "to_upgrade" 2.510
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.910
Then the running Tails is installed on USB drive "to_upgrade" 25.569
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:330 6.894
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.091
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.096
Then all tps features from the old Tails version are active 1.596
And Tails is running from USB drive "to_upgrade" 0.302
And the boot device has safe access rights 3.015
And the expected persistent files created with the old Tails version are present in the filesystem 1.371
And all persistent directories from the old Tails version have safe access rights 2.519
After features/support/hooks.rb:330 1.284
After features/support/hooks.rb:100 0.010
6:30.199
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 10.927
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.059
And Tor is ready 23.274
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.453
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.423
Given I shutdown Tails and wait for the computer to power off 8.623
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.596
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.943
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.258
When the network is plugged 0.069
And Tor is ready 20.104
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.399
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.741
Given I shutdown Tails and wait for the computer to power off 4.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.965
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.943
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.288
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.063
And Tor is ready 15.779
Then the Upgrader considers the system as up-to-date 0.296
# 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.388
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.570
After features/support/hooks.rb:330 0.672
After features/support/hooks.rb:100 0.019
33.966
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.813
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.455
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 17.147
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.358
After features/support/hooks.rb:330 1.626
After features/support/hooks.rb:100 0.000