Project Number Date
test_Tails_ISO_stable 5648 15 May 2025, 09:09

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:10.458 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:6.169
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.457
When I start Tails from USB drive "old" with network unplugged 1:30.620
Then the boot device has safe access rights 3.656
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.368
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:330 3.797
After features/support/hooks.rb:100 0.011
Tags: @product
2:14.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:31.691
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 30.662
And I take note of which tps features are available 2.282
Then a Tails persistence partition exists on USB drive "old" 0.982
And I shutdown Tails and wait for the computer to power off 8.458
After features/support/hooks.rb:330 0.197
After features/support/hooks.rb:100 0.014
Tags: @product
3:7.099
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 1.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.554
Then Tails is running from USB drive "old" 0.441
And all tps features are active 3.509
When I write some files expected to persist 1.756
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.603
And I take note of which tps features are available 1.540
And I shutdown Tails and wait for the computer to power off 4.445
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.422
After features/support/hooks.rb:330 0.089
After features/support/hooks.rb:100 0.024
Tags: @product
2:35.320
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 11.651
And I log in to a new session 20.647
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.745
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.413
Then the running Tails is installed on USB drive "to_upgrade" 20.867
And I unplug USB drive "to_upgrade" 0.292
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:330 2.234
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.608
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.242
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.519
Then all tps features from the old Tails version are active 1.576
And Tails is running from USB drive "to_upgrade" 0.393
And the boot device has safe access rights 3.810
And the expected persistent files created with the old Tails version are present in the filesystem 1.590
And all persistent directories from the old Tails version have safe access rights 2.475
After features/support/hooks.rb:330 1.363
After features/support/hooks.rb:100 0.069
Tags: @product @automatic_upgrade
7:2.930
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 10.715
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.364
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.068
And Tor is ready 19.615
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.184
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.236
Given I shutdown Tails and wait for the computer to power off 9.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.188
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.344
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.244
When the network is plugged 0.068
And Tor is ready 46.998
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.608
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.535
Given I shutdown Tails and wait for the computer to power off 4.463
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.756
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.115
And the file system changes introduced in version 6.3~testoverlayfs are present 0.581
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.419
When the network is plugged 0.070
And Tor is ready 19.995
Then the Upgrader considers the system as up-to-date 0.311
# 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.897
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.589
After features/support/hooks.rb:330 0.900
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
39.705
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 10.837
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.546
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 19.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.416
After features/support/hooks.rb:330 1.261
After features/support/hooks.rb:100 0.000