Project Number Date
test_Tails_ISO_devel 3677 02 Feb 2025, 17:34

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:5.662 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:20.394
Before features/support/hooks.rb:269 0.003
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.173
When I start Tails from USB drive "old" with network unplugged 1:43.646
Then the boot device has safe access rights 3.185
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.098
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:326 9.080
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.783
Before features/support/hooks.rb:269 0.003
Given a computer 0.602
And I start Tails from USB drive "old" with network unplugged and I login 1:24.443
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 35.864
And I take note of which tps features are available 1.367
Then a Tails persistence partition exists on USB drive "old" 0.768
And I shutdown Tails and wait for the computer to power off 8.385
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.006
Tags: @product
2:58.923
Before features/support/hooks.rb:269 0.002
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.040
Then Tails is running from USB drive "old" 0.938
And all tps features are active 2.015
When I write some files expected to persist 1.798
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 2.795
And I take note of which tps features are available 0.463
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.827
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.006
Tags: @product
2:25.414
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.287
And I log in to a new session 18.006
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.012
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.830
Then the running Tails is installed on USB drive "to_upgrade" 18.382
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.249
After features/support/hooks.rb:326 3.045
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.997
Before features/support/hooks.rb:269 0.002
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.816
Then all tps features from the old Tails version are active 1.662
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.287
And the expected persistent files created with the old Tails version are present in the filesystem 1.698
And all persistent directories from the old Tails version have safe access rights 3.008
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:21.342
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.549
And no SquashFS delta is installed 0.166
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.533
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.121
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.066
And Tor is ready 22.065
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.942
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.515
Given I shutdown Tails and wait for the computer to power off 8.426
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.637
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.462
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.304
When the network is plugged 0.068
And Tor is ready 21.006
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.412
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.142
Given I shutdown Tails and wait for the computer to power off 4.419
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.507
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.068
And Tor is ready 20.148
Then the Upgrader considers the system as up-to-date 0.370
# 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.448
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.122
After features/support/hooks.rb:326 1.026
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
33.806
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.938
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.151
But a current signing key is available on our website 0.000
When the network is plugged 0.133
And Tor is ready 18.230
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.956
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.000