Project Number Date
test_Tails_ISO_stable 5750 30 Jun 2025, 10:42

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:5.558 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:56.356
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 41.533
When I start Tails from USB drive "old" with network unplugged 2:4.277
Then the boot device has safe access rights 6.956
And Tails is running from USB drive "old" 0.953
And there is no persistence partition on USB drive "old" 0.147
And process "udev-watchdog" is running 0.204
And udev-watchdog is monitoring the correct device 0.682
And I unplug USB drive "old" 0.298
After features/support/hooks.rb:330 3.825
After features/support/hooks.rb:100 0.017
Tags: @product
3:0.129
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.279
And I start Tails from USB drive "old" with network unplugged and I login 1:55.487
Then Tails is running from USB drive "old" 0.580
And I create a persistent partition 47.031
And I take note of which tps features are available 3.734
Then a Tails persistence partition exists on USB drive "old" 3.412
And I shutdown Tails and wait for the computer to power off 9.602
After features/support/hooks.rb:330 0.230
After features/support/hooks.rb:100 0.010
Tags: @product
4:2.248
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:4.653
Then Tails is running from USB drive "old" 4.169
And all tps features are active 4.239
When I write some files expected to persist 2.812
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 3.211
And I take note of which tps features are available 0.591
And I shutdown Tails and wait for the computer to power off 4.685
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 36.960
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
3:9.783
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 16.561
And I log in to a new session 22.801
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.126
And I plug USB drive "to_upgrade" 6.101
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.891
Then the running Tails is installed on USB drive "to_upgrade" 32.448
And I unplug USB drive "to_upgrade" 0.256
And I unplug USB drive "__internal" 0.595
After features/support/hooks.rb:330 3.911
After features/support/hooks.rb:100 0.000
Tags: @product
3:1.915
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.246
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:45.450
Then all tps features from the old Tails version are active 2.021
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 9.035
And the expected persistent files created with the old Tails version are present in the filesystem 2.333
And all persistent directories from the old Tails version have safe access rights 2.497
After features/support/hooks.rb:330 0.758
After features/support/hooks.rb:100 0.011
9:4.719
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 18.562
And no SquashFS delta is installed 0.208
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.383
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.075
And Tor is ready 32.722
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.885
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 21.448
Given I shutdown Tails and wait for the computer to power off 14.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:48.828
Then Tails is running version 6.2~testoverlayfs 0.035
And all tps features are active 2.823
And the file system changes introduced in version 6.2~testoverlayfs are present 0.606
And only the 6.2~testoverlayfs SquashFS delta is installed 0.546
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 1.126
# 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 1.051
When the network is plugged 0.207
And Tor is ready 25.840
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.032
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.157
Given I shutdown Tails and wait for the computer to power off 7.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:46.864
Then Tails is running version 6.3~testoverlayfs 0.047
And all tps features are active 2.676
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.400
When the network is plugged 0.069
And Tor is ready 23.701
Then the Upgrader considers the system as up-to-date 0.365
# 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 21.038
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.814
After features/support/hooks.rb:330 3.118
After features/support/hooks.rb:100 0.298
50.406
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.061
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.138
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.106
And Tor is ready 26.690
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.938
After features/support/hooks.rb:330 0.926
After features/support/hooks.rb:100 0.000