Project Number Date
test_Tails_ISO_stable 5335 14 Dec 2024, 12:33

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:47.113 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:9.072
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.081
And I write an old version of the Tails USB image to disk "old" 30.270
When I start Tails from USB drive "old" with network unplugged 1:33.529
Then the boot device has safe access rights 2.998
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.535
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.613
Before features/support/hooks.rb:269 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:22.327
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 31.486
And I take note of which tps features are available 1.842
Then a Tails persistence partition exists on USB drive "old" 0.733
And I shutdown Tails and wait for the computer to power off 8.690
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.080
Before features/support/hooks.rb:269 0.005
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.676
Then Tails is running from USB drive "old" 0.345
And all tps features are active 1.846
When I write some files expected to persist 1.575
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.344
And all persistent directories from the old Tails version have safe access rights 2.108
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.293
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.979
After features/support/hooks.rb:326 0.115
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.343
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.308
And I log in to a new session 20.558
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.981
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.626
Then the running Tails is installed on USB drive "to_upgrade" 19.993
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 1.969
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.236
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.914
Then all tps features from the old Tails version are active 1.589
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.279
And the expected persistent files created with the old Tails version are present in the filesystem 1.522
And all persistent directories from the old Tails version have safe access rights 2.424
After features/support/hooks.rb:326 0.934
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:29.382
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 11.194
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.409
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
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.470
When the network is plugged 0.077
And Tor is ready 21.891
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.975
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.188
Given I shutdown Tails and wait for the computer to power off 8.480
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.178
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.209
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.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.263
When the network is plugged 0.093
And Tor is ready 16.059
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.789
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.981
Given I shutdown Tails and wait for the computer to power off 4.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.979
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.170
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.103
And Tor is ready 20.868
Then the Upgrader considers the system as up-to-date 0.307
# 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.950
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.961
After features/support/hooks.rb:326 0.724
After features/support/hooks.rb:100 0.059
Tags: @product @automatic_upgrade
33.385
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.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.787
But a current signing key is available on our website 0.000
When the network is plugged 0.128
And Tor is ready 17.038
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.000
After features/support/hooks.rb:326 0.866
After features/support/hooks.rb:100 0.000