Project Number Date
test_Tails_ISO_devel 3827 21 May 2025, 13:07

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 20:3.211 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:14.640
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.280
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.800
When I start Tails from USB drive "old" with network unplugged 1:36.947
Then the boot device has safe access rights 3.404
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.360
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 7.271
After features/support/hooks.rb:100 0.012
Tags: @product
2:23.424
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.306
And I start Tails from USB drive "old" with network unplugged and I login 1:38.737
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 32.390
And I take note of which tps features are available 1.882
Then a Tails persistence partition exists on USB drive "old" 0.916
And I shutdown Tails and wait for the computer to power off 8.811
After features/support/hooks.rb:330 0.163
After features/support/hooks.rb:100 0.011
Tags: @product
3:5.219
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.226
Then Tails is running from USB drive "old" 0.513
And all tps features are active 2.975
When I write some files expected to persist 1.894
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.339
And all persistence configuration files have safe access rights 0.766
And all persistent directories from the old Tails version have safe access rights 2.840
And I take note of which tps features are available 0.500
And I shutdown Tails and wait for the computer to power off 6.576
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.377
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.011
Tags: @product
2:42.506
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 12.775
And I log in to a new session 19.361
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.926
And I plug USB drive "to_upgrade" 2.503
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.634
Then the running Tails is installed on USB drive "to_upgrade" 28.874
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 2.609
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.857
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.855
Then all tps features from the old Tails version are active 1.554
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.436
And the expected persistent files created with the old Tails version are present in the filesystem 1.547
And all persistent directories from the old Tails version have safe access rights 2.925
After features/support/hooks.rb:330 0.879
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:36.536
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.241
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.430
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.921
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.255
When the network is plugged 0.121
And Tor is ready 20.563
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.153
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.479
Given I shutdown Tails and wait for the computer to power off 10.691
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.178
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.218
And the file system changes introduced in version 6.2~testoverlayfs are present 0.354
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.418
When the network is plugged 0.064
And Tor is ready 22.699
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.856
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.518
Given I shutdown Tails and wait for the computer to power off 4.440
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.500
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.315
And the file system changes introduced in version 6.3~testoverlayfs are present 0.558
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.389
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.080
And Tor is ready 19.811
Then the Upgrader considers the system as up-to-date 0.317
# 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.266
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.758
After features/support/hooks.rb:330 0.856
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
39.027
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.218
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.619
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the signing key used by the Upgrader is outdated 0.148
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 20.641
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.192
After features/support/hooks.rb:330 1.161
After features/support/hooks.rb:100 0.000