Project Number Date
test_Tails_ISO_improved-new-identity-scenario 12 11 May 2025, 13:32

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:41.144 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.078
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.256
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 29.551
When I start Tails from USB drive "old" with network unplugged 1:38.930
Then the boot device has safe access rights 3.224
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:330 7.180
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:37.108
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 36.265
And I take note of which tps features are available 2.464
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.498
After features/support/hooks.rb:330 0.201
After features/support/hooks.rb:100 0.012
Tags: @product
3:5.881
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.411
Then Tails is running from USB drive "old" 0.378
And all tps features are active 2.227
When I write some files expected to persist 1.792
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.363
And all persistent directories from the old Tails version have safe access rights 3.931
And I take note of which tps features are available 0.506
And I shutdown Tails and wait for the computer to power off 4.562
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.282
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.524
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.135
And I log in to a new session 19.365
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.645
And I plug USB drive "to_upgrade" 2.513
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.516
Then the running Tails is installed on USB drive "to_upgrade" 23.907
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:330 3.753
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.841
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.582
Then all tps features from the old Tails version are active 2.378
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.405
And the expected persistent files created with the old Tails version are present in the filesystem 1.360
And all persistent directories from the old Tails version have safe access rights 2.544
After features/support/hooks.rb:330 1.312
After features/support/hooks.rb:100 0.008
8:11.915
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 12.313
And no SquashFS delta is installed 0.481
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.806
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.358
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.454
When the network is plugged 0.075
And Tor is ready 20.716
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.395
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.733
Given I shutdown Tails and wait for the computer to power off 1:24.083
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.320
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.578
And the file system changes introduced in version 6.2~testoverlayfs are present 0.534
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.339
# 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.363
When the network is plugged 0.122
And Tor is ready 20.050
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.078
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.840
Given I shutdown Tails and wait for the computer to power off 6.644
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.014
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.555
And the file system changes introduced in version 6.3~testoverlayfs are present 0.526
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.084
And Tor is ready 18.308
Then the Upgrader considers the system as up-to-date 10.929
# 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.473
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.897
After features/support/hooks.rb:330 0.720
After features/support/hooks.rb:100 0.023
44.226
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 9.869
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.563
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.104
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 24.600
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.924
After features/support/hooks.rb:330 0.660
After features/support/hooks.rb:100 0.000