Project Number Date
test_Tails_ISO_stable 5365 03 Jan 2025, 12:58

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:50.537 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:57.495
Before features/support/hooks.rb:269 0.005
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.200
When I start Tails from USB drive "old" with network unplugged 1:23.942
Then the boot device has safe access rights 3.034
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 7.051
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.300
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:20.854
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 32.429
And I take note of which tps features are available 1.396
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 8.298
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.862
Before features/support/hooks.rb:269 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.555
Then Tails is running from USB drive "old" 0.321
And all tps features are active 1.945
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.248
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.426
And I take note of which tps features are available 0.615
And I shutdown Tails and wait for the computer to power off 4.166
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.173
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.653
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.331
And I log in to a new session 19.816
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.580
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.949
Then the running Tails is installed on USB drive "to_upgrade" 22.108
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 2.188
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.443
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.026
Then all tps features from the old Tails version are active 1.517
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 2.840
And the expected persistent files created with the old Tails version are present in the filesystem 1.330
And all persistent directories from the old Tails version have safe access rights 2.216
After features/support/hooks.rb:326 0.838
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:39.506
Before features/support/hooks.rb:269 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.812
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.097
And Tor is ready 20.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.625
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.850
Given I shutdown Tails and wait for the computer to power off 1:21.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.103
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.090
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.259
When the network is plugged 0.067
And Tor is ready 16.754
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.849
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.724
Given I shutdown Tails and wait for the computer to power off 4.296
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.635
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.939
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.419
When the network is plugged 0.072
And Tor is ready 21.314
Then the Upgrader considers the system as up-to-date 0.321
# 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.688
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.118
After features/support/hooks.rb:326 0.714
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
33.274
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.213
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 17.474
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.034
After features/support/hooks.rb:326 0.661
After features/support/hooks.rb:100 0.000