Project Number Date
test_Tails_ISO_stable 5454 12 Feb 2025, 14:15

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:6.646 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.751
Before features/support/hooks.rb:269 0.004
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.034
When I start Tails from USB drive "old" with network unplugged 1:24.508
Then the boot device has safe access rights 2.939
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 0.945
After features/support/hooks.rb:100 0.013
Tags: @product
2:7.751
Before features/support/hooks.rb:269 0.003
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:23.855
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 32.688
And I take note of which tps features are available 1.514
Then a Tails persistence partition exists on USB drive "old" 0.880
And I shutdown Tails and wait for the computer to power off 8.308
After features/support/hooks.rb:326 0.233
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.374
Before features/support/hooks.rb:269 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.632
Then Tails is running from USB drive "old" 0.368
And all tps features are active 1.926
When I write some files expected to persist 1.728
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.295
And I take note of which tps features are available 0.388
And I shutdown Tails and wait for the computer to power off 4.288
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.941
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
2:26.105
Before features/support/hooks.rb:269 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 9.643
And I log in to a new session 18.419
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.171
And I plug USB drive "to_upgrade" 2.485
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.611
Then the running Tails is installed on USB drive "to_upgrade" 18.384
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 3.257
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.345
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.010
Then all tps features from the old Tails version are active 1.645
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.448
And the expected persistent files created with the old Tails version are present in the filesystem 1.374
And all persistent directories from the old Tails version have safe access rights 2.320
After features/support/hooks.rb:326 0.891
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:45.567
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.566
And no SquashFS delta is installed 0.163
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.064
And Tor is ready 20.013
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.467
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.204
Given I shutdown Tails and wait for the computer to power off 8.584
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.290
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.267
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.279
When the network is plugged 0.059
And Tor is ready 17.986
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.674
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.315
Given I shutdown Tails and wait for the computer to power off 4.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.940
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.965
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.074
And Tor is ready 21.212
Then the Upgrader considers the system as up-to-date 0.310
# 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.587
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.232
After features/support/hooks.rb:326 0.791
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
32.750
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.068
And Tor is ready 15.588
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.615
After features/support/hooks.rb:326 1.268
After features/support/hooks.rb:100 0.000