Project Number Date
test_Tails_ISO_devel 3862 10 Jun 2025, 21:39

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 21:28.170 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:49.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.249
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 36.603
When I start Tails from USB drive "old" with network unplugged 2:6.920
Then the boot device has safe access rights 3.724
And Tails is running from USB drive "old" 0.395
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.128
And udev-watchdog is monitoring the correct device 0.350
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:330 11.416
After features/support/hooks.rb:100 0.012
Tags: @product
2:23.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login 1:35.591
Then Tails is running from USB drive "old" 0.423
And I create a persistent partition 34.603
And I take note of which tps features are available 2.602
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.770
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.014
Tags: @product
3:5.003
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.632
Then Tails is running from USB drive "old" 0.387
And all tps features are active 2.401
When I write some files expected to persist 1.943
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.475
And all persistent directories from the old Tails version have safe access rights 2.510
And I take note of which tps features are available 0.447
And I shutdown Tails and wait for the computer to power off 4.523
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.203
After features/support/hooks.rb:330 0.179
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.544
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 17.005
And I log in to a new session 22.147
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.284
And I plug USB drive "to_upgrade" 2.656
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.953
Then the running Tails is installed on USB drive "to_upgrade" 30.081
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 7.065
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.160
Then all tps features from the old Tails version are active 1.908
And Tails is running from USB drive "to_upgrade" 0.566
And the boot device has safe access rights 4.141
And the expected persistent files created with the old Tails version are present in the filesystem 1.780
And all persistent directories from the old Tails version have safe access rights 3.010
After features/support/hooks.rb:330 1.426
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
7:1.815
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 13.455
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.522
When the network is plugged 0.097
And Tor is ready 24.100
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.017
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.752
Given I shutdown Tails and wait for the computer to power off 11.246
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.982
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.706
And the file system changes introduced in version 6.2~testoverlayfs are present 0.379
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.280
When the network is plugged 0.083
And Tor is ready 19.663
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.967
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.010
Given I shutdown Tails and wait for the computer to power off 4.767
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.964
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.330
And the file system changes introduced in version 6.3~testoverlayfs are present 0.780
And only the 6.3~testoverlayfs SquashFS delta is installed 0.137
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.398
When the network is plugged 0.066
And Tor is ready 20.632
Then the Upgrader considers the system as up-to-date 0.401
# 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 16.510
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.877
After features/support/hooks.rb:330 0.842
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
42.109
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 with a persistent partition enabled and logged in 12.213
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.595
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 20.620
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.457
After features/support/hooks.rb:330 0.652
After features/support/hooks.rb:100 0.000