Project Number Date
test_Tails_ISO_feature-arti 100 28 Jun 2025, 18:09

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.248 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:11.080
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.407
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.072
And I write an old version of the Tails USB image to disk "old" 28.689
When I start Tails from USB drive "old" with network unplugged 1:36.606
Then the boot device has safe access rights 3.235
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 7.098
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.432
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:40.226
Then Tails is running from USB drive "old" 0.924
And I create a persistent partition 33.481
And I take note of which tps features are available 2.146
Then a Tails persistence partition exists on USB drive "old" 0.854
And I shutdown Tails and wait for the computer to power off 7.608
After features/support/hooks.rb:330 0.142
After features/support/hooks.rb:100 0.008
Tags: @product
3:5.304
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.958
Then Tails is running from USB drive "old" 0.376
And all tps features are active 2.045
When I write some files expected to persist 1.788
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 3.139
And I take note of which tps features are available 0.399
And I shutdown Tails and wait for the computer to power off 5.566
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.155
After features/support/hooks.rb:330 0.102
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.831
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 9.872
And I log in to a new session 20.935
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.167
And I plug USB drive "to_upgrade" 2.648
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.305
Then the running Tails is installed on USB drive "to_upgrade" 28.512
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:330 1.001
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.155
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.462
Then all tps features from the old Tails version are active 1.839
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 3.232
And the expected persistent files created with the old Tails version are present in the filesystem 1.457
And all persistent directories from the old Tails version have safe access rights 2.670
After features/support/hooks.rb:330 1.528
After features/support/hooks.rb:100 0.094
Tags: @product @automatic_upgrade
7:26.054
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.084
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.393
And no SquashFS delta is installed 0.482
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.484
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.063
And Tor is ready 24.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.771
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.403
Given I shutdown Tails and wait for the computer to power off 12.161
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.574
Then Tails is running version 6.2~testoverlayfs 0.041
And all tps features are active 2.396
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.383
# 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.601
When the network is plugged 0.200
And Tor is ready 21.428
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.968
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.777
Given I shutdown Tails and wait for the computer to power off 6.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.493
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.275
And the file system changes introduced in version 6.3~testoverlayfs are present 0.504
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.082
And Tor is ready 20.141
Then the Upgrader considers the system as up-to-date 0.374
# 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.607
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.787
After features/support/hooks.rb:330 0.927
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
45.390
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.615
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.112
And Tor is ready 24.362
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.870
After features/support/hooks.rb:330 1.166
After features/support/hooks.rb:100 0.000