Project Number Date
test_Tails_ISO_feature-arti 99 27 Jun 2025, 18:54

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 22:51.026 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.354
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.088
And I write an old version of the Tails USB image to disk "old" 30.342
When I start Tails from USB drive "old" with network unplugged 1:48.365
Then the boot device has safe access rights 4.137
And Tails is running from USB drive "old" 0.411
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:330 3.737
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.145
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login 1:40.283
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 38.437
And I take note of which tps features are available 2.826
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 8.163
After features/support/hooks.rb:330 0.205
After features/support/hooks.rb:100 0.011
Tags: @product
3:39.030
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.261
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:50.377
Then Tails is running from USB drive "old" 0.403
And all tps features are active 2.998
When I write some files expected to persist 2.416
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.731
And all persistent directories from the old Tails version have safe access rights 3.377
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 6.454
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.281
After features/support/hooks.rb:330 0.206
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.352
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.288
And I log in to a new session 22.348
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.543
And I plug USB drive "to_upgrade" 2.821
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.801
Then the running Tails is installed on USB drive "to_upgrade" 30.145
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 2.609
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.817
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Given a computer 0.633
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.609
Then all tps features from the old Tails version are active 2.610
And Tails is running from USB drive "to_upgrade" 0.732
And the boot device has safe access rights 4.013
And the expected persistent files created with the old Tails version are present in the filesystem 1.566
And all persistent directories from the old Tails version have safe access rights 2.651
After features/support/hooks.rb:330 1.294
After features/support/hooks.rb:100 0.009
8:7.698
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 13.386
And no SquashFS delta is installed 0.181
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.413
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.572
When the network is plugged 0.092
And Tor is ready 25.978
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.498
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.041
Given I shutdown Tails and wait for the computer to power off 14.937
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.615
Then Tails is running version 6.2~testoverlayfs 0.076
And all tps features are active 3.270
And the file system changes introduced in version 6.2~testoverlayfs are present 0.368
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.416
# 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.356
When the network is plugged 0.079
And Tor is ready 22.140
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.081
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.335
Given I shutdown Tails and wait for the computer to power off 6.928
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.880
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.976
And the file system changes introduced in version 6.3~testoverlayfs are present 0.986
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.380
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.351
When the network is plugged 0.083
And Tor is ready 28.037
Then the Upgrader considers the system as up-to-date 0.301
# 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 19.125
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.142
After features/support/hooks.rb:330 1.479
After features/support/hooks.rb:100 0.052
44.627
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 with a persistent partition enabled and logged in 12.363
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.497
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.121
And the signing key used by the Upgrader is outdated 0.088
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 22.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.434
After features/support/hooks.rb:330 0.892
After features/support/hooks.rb:100 0.000