Project Number Date
test_Tails_ISO_devel 3891 29 Jun 2025, 13:55

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 24:42.872 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:5.470
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.102
And I write an old version of the Tails USB image to disk "old" 39.727
When I start Tails from USB drive "old" with network unplugged 2:20.039
Then the boot device has safe access rights 3.284
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:330 3.771
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.190
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:57.288
Then Tails is running from USB drive "old" 0.616
And I create a persistent partition 48.790
And I take note of which tps features are available 3.439
Then a Tails persistence partition exists on USB drive "old" 1.141
And I shutdown Tails and wait for the computer to power off 8.688
After features/support/hooks.rb:330 0.190
After features/support/hooks.rb:100 0.011
Tags: @product
4:5.723
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.753
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:6.888
Then Tails is running from USB drive "old" 1.137
And all tps features are active 2.765
When I write some files expected to persist 1.918
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.970
And I take note of which tps features are available 0.599
And I shutdown Tails and wait for the computer to power off 11.092
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 36.920
After features/support/hooks.rb:330 0.342
After features/support/hooks.rb:100 0.026
Tags: @product
3:8.905
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 without a persistent partition and stopped at Tails Greeter's login screen 12.211
And I log in to a new session 25.588
And I clone USB drive "old" to a new USB drive "to_upgrade" 5.792
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.809
Then the running Tails is installed on USB drive "to_upgrade" 30.648
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:330 2.483
After features/support/hooks.rb:100 0.000
Tags: @product
2:42.067
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:31.970
Then all tps features from the old Tails version are active 1.762
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.265
And the expected persistent files created with the old Tails version are present in the filesystem 1.847
And all persistent directories from the old Tails version have safe access rights 2.708
After features/support/hooks.rb:330 2.337
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
7:35.461
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 with a persistent partition enabled and logged in 12.220
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.427
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.369
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.079
And Tor is ready 23.430
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.612
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.219
Given I shutdown Tails and wait for the computer to power off 12.178
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.176
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.286
And the file system changes introduced in version 6.2~testoverlayfs are present 0.523
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.565
When the network is plugged 0.097
And Tor is ready 21.791
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.506
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.591
Given I shutdown Tails and wait for the computer to power off 7.237
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.381
Then Tails is running version 6.3~testoverlayfs 0.066
And all tps features are active 2.414
And the file system changes introduced in version 6.3~testoverlayfs are present 0.582
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.621
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.346
When the network is plugged 0.064
And Tor is ready 22.371
Then the Upgrader considers the system as up-to-date 0.330
# 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 19.181
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.573
After features/support/hooks.rb:330 0.845
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
1:5.051
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 12.838
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
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.069
And Tor is ready 50.797
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.837
After features/support/hooks.rb:330 0.913
After features/support/hooks.rb:100 0.000