Project Number Date
test_Tails_ISO_stable 5425 28 Jan 2025, 12:52

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:24.381 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:36.962
Before features/support/hooks.rb:269 0.005
Given a computer 0.256
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 50.806
When I start Tails from USB drive "old" with network unplugged 1:39.932
Then the boot device has safe access rights 3.635
And Tails is running from USB drive "old" 0.414
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.358
And I unplug USB drive "old" 0.229
After features/support/hooks.rb:326 7.422
After features/support/hooks.rb:100 0.012
Tags: @product
2:24.878
Before features/support/hooks.rb:269 0.005
Given a computer 0.291
And I start Tails from USB drive "old" with network unplugged and I login 1:37.554
Then Tails is running from USB drive "old" 0.397
And I create a persistent partition 35.505
And I take note of which tps features are available 1.703
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.575
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.008
Tags: @product
3:2.891
Before features/support/hooks.rb:269 0.005
Given a computer 0.277
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.414
Then Tails is running from USB drive "old" 0.435
And all tps features are active 2.331
When I write some files expected to persist 1.767
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 2.469
And I take note of which tps features are available 0.550
And I shutdown Tails and wait for the computer to power off 4.389
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.614
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.222
Before features/support/hooks.rb:269 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 26.342
And I log in to a new session 20.656
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.836
And I plug USB drive "to_upgrade" 2.540
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.748
Then the running Tails is installed on USB drive "to_upgrade" 26.576
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.299
After features/support/hooks.rb:326 3.546
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.698
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.043
Then all tps features from the old Tails version are active 1.786
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 4.011
And the expected persistent files created with the old Tails version are present in the filesystem 1.622
And all persistent directories from the old Tails version have safe access rights 2.674
After features/support/hooks.rb:326 0.882
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:4.372
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.400
And no SquashFS delta is installed 0.465
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.463
When the network is plugged 0.082
And Tor is ready 19.119
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.290
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.132
Given I shutdown Tails and wait for the computer to power off 9.158
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:30.139
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.631
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
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.349
# 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.389
When the network is plugged 0.080
And Tor is ready 17.554
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.979
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.724
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.886
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.096
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.431
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.071
And Tor is ready 18.213
Then the Upgrader considers the system as up-to-date 10.854
# 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 15.391
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.116
After features/support/hooks.rb:326 0.874
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
57.355
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.612
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.753
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 45.110
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.657
After features/support/hooks.rb:326 0.783
After features/support/hooks.rb:100 0.000