Project Number Date
test_Tails_ISO_devel 3817 17 May 2025, 13:04

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:9.346 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:13.303
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.260
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.604
When I start Tails from USB drive "old" with network unplugged 1:37.017
Then the boot device has safe access rights 3.290
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:330 3.672
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.533
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.812
And I start Tails from USB drive "old" with network unplugged and I login 1:27.283
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 30.728
And I take note of which tps features are available 2.555
Then a Tails persistence partition exists on USB drive "old" 0.910
And I shutdown Tails and wait for the computer to power off 6.873
After features/support/hooks.rb:330 0.174
After features/support/hooks.rb:100 0.007
Tags: @product
3:1.279
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.192
Then Tails is running from USB drive "old" 0.507
And all tps features are active 2.158
When I write some files expected to persist 1.750
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.471
And all persistent directories from the old Tails version have safe access rights 2.651
And I take note of which tps features are available 0.490
And I shutdown Tails and wait for the computer to power off 4.748
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.857
After features/support/hooks.rb:330 0.117
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.472
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.166
And I log in to a new session 19.322
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.096
And I plug USB drive "to_upgrade" 2.530
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.337
Then the running Tails is installed on USB drive "to_upgrade" 25.585
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 3.512
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.170
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.217
Then all tps features from the old Tails version are active 1.665
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.749
And the expected persistent files created with the old Tails version are present in the filesystem 1.491
And all persistent directories from the old Tails version have safe access rights 2.501
After features/support/hooks.rb:330 0.599
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:9.401
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 11.599
And no SquashFS delta is installed 0.295
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.338
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.463
When the network is plugged 0.071
And Tor is ready 50.861
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.499
Given I shutdown Tails and wait for the computer to power off 11.606
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.267
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.409
And the file system changes introduced in version 6.2~testoverlayfs are present 0.338
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.291
When the network is plugged 0.093
And Tor is ready 20.349
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.211
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.183
Given I shutdown Tails and wait for the computer to power off 4.631
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.908
Then Tails is running version 6.3~testoverlayfs 0.036
And all tps features are active 2.062
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.130
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.063
And Tor is ready 19.621
Then the Upgrader considers the system as up-to-date 0.307
# 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 17.104
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.913
After features/support/hooks.rb:330 0.814
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
40.185
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 11.021
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.670
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.100
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 19.844
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.365
After features/support/hooks.rb:330 1.107
After features/support/hooks.rb:100 0.000