Project Number Date
test_Tails_ISO_devel 3773 09 Apr 2025, 15:20

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:0.354 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:25.798
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 33.693
When I start Tails from USB drive "old" with network unplugged 1:46.183
Then the boot device has safe access rights 3.456
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.130
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:330 3.803
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.272
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:38.768
Then Tails is running from USB drive "old" 0.445
And I create a persistent partition 32.711
And I take note of which tps features are available 2.199
Then a Tails persistence partition exists on USB drive "old" 0.847
And I shutdown Tails and wait for the computer to power off 9.084
After features/support/hooks.rb:330 0.228
After features/support/hooks.rb:100 0.018
Tags: @product
3:1.111
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.879
Then Tails is running from USB drive "old" 0.427
And all tps features are active 2.627
When I write some files expected to persist 2.296
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.377
And all persistence configuration files have safe access rights 0.523
And all persistent directories from the old Tails version have safe access rights 2.957
And I take note of which tps features are available 0.659
And I shutdown Tails and wait for the computer to power off 6.248
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.879
After features/support/hooks.rb:330 0.124
After features/support/hooks.rb:100 0.013
Tags: @product
3:0.873
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 27.927
And I log in to a new session 20.351
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.965
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.341
Then the running Tails is installed on USB drive "to_upgrade" 27.297
And I unplug USB drive "to_upgrade" 0.288
And I unplug USB drive "__internal" 0.255
After features/support/hooks.rb:330 2.232
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.153
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.287
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.822
Then all tps features from the old Tails version are active 1.849
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.669
And the expected persistent files created with the old Tails version are present in the filesystem 1.612
And all persistent directories from the old Tails version have safe access rights 2.553
After features/support/hooks.rb:330 1.446
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:6.587
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.637
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.522
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.398
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.529
When the network is plugged 0.081
And Tor is ready 22.406
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.745
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.319
Given I shutdown Tails and wait for the computer to power off 13.678
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.675
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.294
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.395
# 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.532
When the network is plugged 0.066
And Tor is ready 21.324
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.619
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.850
Given I shutdown Tails and wait for the computer to power off 6.586
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.446
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.089
And the file system changes introduced in version 6.3~testoverlayfs are present 0.605
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.393
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.067
And Tor is ready 17.250
Then the Upgrader considers the system as up-to-date 11.021
# 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.093
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.009
After features/support/hooks.rb:330 0.745
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.555
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 10.284
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.442
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 16.616
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.888
After features/support/hooks.rb:330 1.936
After features/support/hooks.rb:100 0.000