Project Number Date
test_Tails_ISO_devel 3715 03 Mar 2025, 13:12

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 20:32.802 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:47.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 1.416
And I create a 7200 MiB disk named "old" 0.634
And I plug USB drive "old" 1.162
And I write an old version of the Tails USB image to disk "old" 58.317
When I start Tails from USB drive "old" with network unplugged 1:42.059
Then the boot device has safe access rights 3.276
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:330 8.707
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.522
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:31.846
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 33.297
And I take note of which tps features are available 1.521
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.470
After features/support/hooks.rb:330 0.251
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.644
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.000
Then Tails is running from USB drive "old" 0.751
And all tps features are active 1.940
When I write some files expected to persist 1.675
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 3.292
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 4.304
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.352
After features/support/hooks.rb:330 0.207
After features/support/hooks.rb:100 0.011
Tags: @product
2:34.904
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.670
And I log in to a new session 20.631
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.633
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.913
Then the running Tails is installed on USB drive "to_upgrade" 22.181
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 2.907
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.476
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.834
Then all tps features from the old Tails version are active 1.856
And Tails is running from USB drive "to_upgrade" 0.414
And the boot device has safe access rights 3.690
And the expected persistent files created with the old Tails version are present in the filesystem 1.628
And all persistent directories from the old Tails version have safe access rights 2.864
After features/support/hooks.rb:330 1.149
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:46.998
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 12.818
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.142
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.359
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.620
When the network is plugged 0.094
And Tor is ready 21.415
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.633
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.480
Given I shutdown Tails and wait for the computer to power off 8.652
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.426
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.404
And the file system changes introduced in version 6.2~testoverlayfs are present 0.452
And only the 6.2~testoverlayfs SquashFS delta is installed 0.115
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.459
# 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.438
When the network is plugged 0.074
And Tor is ready 18.803
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.626
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.125
Given I shutdown Tails and wait for the computer to power off 4.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.644
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.447
And the file system changes introduced in version 6.3~testoverlayfs are present 0.540
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.077
And Tor is ready 17.013
Then the Upgrader considers the system as up-to-date 0.418
# 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.123
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.014
After features/support/hooks.rb:330 1.081
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.308
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 10.404
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.496
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.123
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 19.249
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.885
After features/support/hooks.rb:330 0.671
After features/support/hooks.rb:100 0.000