Project Number Date
test_Tails_ISO_stable 4777 07 Apr 2024, 12:03

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:27.837 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:37.543
Before features/support/hooks.rb:259 0.008
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 19.951
When I start Tails from USB drive "old" with network unplugged 1:12.275
Then the boot device has safe access rights 2.962
And Tails is running from USB drive "old" 0.401
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:305 7.003
After features/support/hooks.rb:89 0.012
Tags: @product
2:0.700
Before features/support/hooks.rb:259 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:16.939
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 33.542
And I take note of which tps features are available 2.554
Then a Tails persistence partition exists on USB drive "old" 0.836
And I shutdown Tails and wait for the computer to power off 6.280
After features/support/hooks.rb:305 0.172
After features/support/hooks.rb:89 0.010
Tags: @product
2:31.091
Before features/support/hooks.rb:259 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:3.613
Then Tails is running from USB drive "old" 0.370
And all tps features are active 2.015
When I write some files expected to persist 1.736
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.542
And I take note of which tps features are available 0.473
And I shutdown Tails and wait for the computer to power off 4.457
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.008
After features/support/hooks.rb:305 0.157
After features/support/hooks.rb:89 0.008
Tags: @product
2:26.782
Before features/support/hooks.rb:259 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 11.825
And I log in to a new session 19.289
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.565
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.951
Then the running Tails is installed on USB drive "to_upgrade" 14.336
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:305 2.326
After features/support/hooks.rb:89 0.000
Tags: @product
2:3.764
Before features/support/hooks.rb:259 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.311
Then all tps features from the old Tails version are active 1.592
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.050
And the expected persistent files created with the old Tails version are present in the filesystem 1.735
And all persistent directories from the old Tails version have safe access rights 2.530
After features/support/hooks.rb:305 0.725
After features/support/hooks.rb:89 0.023
Tags: @product @automatic_upgrade
7:12.648
Before features/support/hooks.rb:259 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.337
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.362
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.043
And Tor is ready 19.823
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.447
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.867
Given I shutdown Tails and wait for the computer to power off 1:12.688
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.455
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.236
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.331
When the network is plugged 0.052
And Tor is ready 16.365
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.641
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.911
Given I shutdown Tails and wait for the computer to power off 4.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.465
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.128
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.048
And Tor is ready 15.061
Then the Upgrader considers the system as up-to-date 0.283
# 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 13.060
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.967
After features/support/hooks.rb:305 0.722
After features/support/hooks.rb:89 0.018
Tags: @product @automatic_upgrade
35.306
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.712
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.671
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 17.097
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.411
After features/support/hooks.rb:305 0.598
After features/support/hooks.rb:89 0.000