Project Number Date
test_Tails_ISO_stable 5444 05 Feb 2025, 17:13

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:26.078 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:49.696
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.793
When I start Tails from USB drive "old" with network unplugged 1:15.465
Then the boot device has safe access rights 3.197
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.493
After features/support/hooks.rb:100 0.024
Tags: @product
2:2.062
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:21.425
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 31.563
And I take note of which tps features are available 1.646
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 6.132
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.449
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.863
Then Tails is running from USB drive "old" 1.226
And all tps features are active 2.285
When I write some files expected to persist 2.599
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.972
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.423
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 6.297
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.721
After features/support/hooks.rb:326 0.088
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.081
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 10.953
And I log in to a new session 21.433
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.695
And I plug USB drive "to_upgrade" 2.351
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.938
Then the running Tails is installed on USB drive "to_upgrade" 19.313
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 0.919
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.492
Before features/support/hooks.rb:269 0.005
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.244
Then all tps features from the old Tails version are active 1.627
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.046
And the expected persistent files created with the old Tails version are present in the filesystem 1.545
And all persistent directories from the old Tails version have safe access rights 2.477
After features/support/hooks.rb:326 0.789
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:20.316
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 11.702
And no SquashFS delta is installed 0.577
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.454
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.727
When the network is plugged 0.076
And Tor is ready 22.997
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.536
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.114
Given I shutdown Tails and wait for the computer to power off 10.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.507
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.245
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.270
When the network is plugged 0.085
And Tor is ready 19.143
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.585
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.008
Given I shutdown Tails and wait for the computer to power off 4.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.801
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.528
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.387
When the network is plugged 0.093
And Tor is ready 17.985
Then the Upgrader considers the system as up-to-date 0.315
# 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.663
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.099
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.980
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.690
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.729
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.064
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 21.892
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.465
After features/support/hooks.rb:326 0.904
After features/support/hooks.rb:100 0.000