Project Number Date
test_Tails_ISO_feature-arti 105 03 Jul 2025, 16:37

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 19:58.971 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:17.119
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 37.397
When I start Tails from USB drive "old" with network unplugged 1:34.496
Then the boot device has safe access rights 2.971
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 3.730
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.520
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:30.395
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 30.628
And I take note of which tps features are available 1.721
Then a Tails persistence partition exists on USB drive "old" 0.694
And I shutdown Tails and wait for the computer to power off 8.549
After features/support/hooks.rb:330 0.197
After features/support/hooks.rb:100 0.046
Tags: @product
2:53.541
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.980
Then Tails is running from USB drive "old" 0.468
And all tps features are active 1.770
When I write some files expected to persist 1.667
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 2.663
And I take note of which tps features are available 0.374
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" 25.406
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.785
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 without a persistent partition and stopped at Tails Greeter's login screen 10.324
And I log in to a new session 19.237
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.395
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.083
Then the running Tails is installed on USB drive "to_upgrade" 29.828
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.277
After features/support/hooks.rb:330 3.322
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.013
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.661
Then all tps features from the old Tails version are active 1.517
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 3.265
And the expected persistent files created with the old Tails version are present in the filesystem 1.483
And all persistent directories from the old Tails version have safe access rights 3.603
After features/support/hooks.rb:330 0.969
After features/support/hooks.rb:100 0.043
6:51.887
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.893
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.512
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.059
And Tor is ready 22.157
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.545
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.690
Given I shutdown Tails and wait for the computer to power off 11.370
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.787
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.236
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.301
When the network is plugged 0.093
And Tor is ready 19.575
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.653
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.037
Given I shutdown Tails and wait for the computer to power off 4.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.905
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.923
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.062
And Tor is ready 22.737
Then the Upgrader considers the system as up-to-date 0.350
# 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.313
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.477
After features/support/hooks.rb:330 0.706
After features/support/hooks.rb:100 0.018
36.104
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 9.887
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 18.414
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.244
After features/support/hooks.rb:330 1.277
After features/support/hooks.rb:100 0.000