Project Number Date
test_Tails_ISO_devel 3621 24 Dec 2024, 12:42

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.488 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:4.662
Before features/support/hooks.rb:269 0.006
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.017
When I start Tails from USB drive "old" with network unplugged 1:29.169
Then the boot device has safe access rights 3.117
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 6.991
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.708
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:23.688
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 32.846
And I take note of which tps features are available 1.455
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 8.343
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.826
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.195
Then Tails is running from USB drive "old" 0.666
And all tps features are active 2.120
When I write some files expected to persist 1.623
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.627
And I take note of which tps features are available 0.424
And I shutdown Tails and wait for the computer to power off 4.267
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.086
After features/support/hooks.rb:326 0.115
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.461
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.306
And I log in to a new session 20.156
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.493
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.031
Then the running Tails is installed on USB drive "to_upgrade" 21.672
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 2.858
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.130
Before features/support/hooks.rb:269 0.007
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.926
Then all tps features from the old Tails version are active 2.039
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.609
And the expected persistent files created with the old Tails version are present in the filesystem 1.398
And all persistent directories from the old Tails version have safe access rights 2.611
After features/support/hooks.rb:326 0.724
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:36.448
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.276
And no SquashFS delta is installed 0.219
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.067
And Tor is ready 18.717
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.699
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.967
Given I shutdown Tails and wait for the computer to power off 10.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.315
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.440
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.275
# 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.391
When the network is plugged 0.080
And Tor is ready 17.032
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.635
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.749
Given I shutdown Tails and wait for the computer to power off 4.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.521
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.095
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.074
And Tor is ready 20.625
Then the Upgrader considers the system as up-to-date 0.309
# 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.113
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.983
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.250
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.682
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.715
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.183
And the signing key used by the Upgrader is outdated 0.726
But a current signing key is available on our website 0.000
When the network is plugged 0.136
And Tor is ready 17.261
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.544
After features/support/hooks.rb:326 0.677
After features/support/hooks.rb:100 0.000