Project Number Date
test_Tails_ISO_20979-pdfarranger 9 04 Jun 2025, 02:47

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 18:54.798 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
1:59.957
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.774
When I start Tails from USB drive "old" with network unplugged 1:26.092
Then the boot device has safe access rights 2.874
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 7.153
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.120
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:21.965
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 29.295
And I take note of which tps features are available 2.423
Then a Tails persistence partition exists on USB drive "old" 0.676
And I shutdown Tails and wait for the computer to power off 8.194
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.008
Tags: @product
2:42.191
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 with persistence enabled 2:3.921
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.986
When I write some files expected to persist 1.746
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.291
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.643
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 6.162
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.041
After features/support/hooks.rb:330 0.134
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.076
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.196
And I log in to a new session 19.090
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.599
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.675
Then the running Tails is installed on USB drive "to_upgrade" 26.611
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 3.509
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.301
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.316
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.777
Then all tps features from the old Tails version are active 1.507
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.310
And the expected persistent files created with the old Tails version are present in the filesystem 1.452
And all persistent directories from the old Tails version have safe access rights 2.604
After features/support/hooks.rb:330 1.298
After features/support/hooks.rb:100 0.008
6:45.614
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.773
And no SquashFS delta is installed 0.415
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.403
When the network is plugged 0.078
And Tor is ready 23.103
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.460
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.199
Given I shutdown Tails and wait for the computer to power off 8.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.111
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.159
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.358
When the network is plugged 0.071
And Tor is ready 46.818
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.584
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.595
Given I shutdown Tails and wait for the computer to power off 4.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.721
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.037
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.068
And Tor is ready 19.460
Then the Upgrader considers the system as up-to-date 0.311
# 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 14.875
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.597
After features/support/hooks.rb:330 0.724
After features/support/hooks.rb:100 0.017
33.535
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.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.731
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 16.053
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.396
After features/support/hooks.rb:330 1.307
After features/support/hooks.rb:100 0.000