Project Number Date
test_Tails_ISO_stable 4724 18 Mar 2024, 13:26

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 17:8.738 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:2.940
Before features/support/hooks.rb:245 0.008
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 40.706
When I start Tails from USB drive "old" with network unplugged 1:16.568
Then the boot device has safe access rights 3.275
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.253
After features/support/hooks.rb:291 6.813
After features/support/hooks.rb:75 0.009
Tags: @product
1:58.578
Before features/support/hooks.rb:245 0.007
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:17.955
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 30.396
And I take note of which tps features are available 1.812
Then a Tails persistence partition exists on USB drive "old" 0.752
And I shutdown Tails and wait for the computer to power off 7.159
After features/support/hooks.rb:291 0.137
After features/support/hooks.rb:75 0.010
Tags: @product
2:24.462
Before features/support/hooks.rb:245 0.007
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:58.978
Then Tails is running from USB drive "old" 0.354
And all tps features are active 1.684
When I write some files expected to persist 1.535
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.213
And I take note of which tps features are available 0.321
And I shutdown Tails and wait for the computer to power off 4.019
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.619
After features/support/hooks.rb:291 0.134
After features/support/hooks.rb:75 0.010
Tags: @product
2:17.396
Before features/support/hooks.rb:245 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 9.923
And I log in to a new session 15.740
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.388
And I plug USB drive "to_upgrade" 2.390
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.958
Then the running Tails is installed on USB drive "to_upgrade" 12.619
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:291 6.536
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.228
Before features/support/hooks.rb:245 0.006
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.758
Then all tps features from the old Tails version are active 1.441
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 2.858
And the expected persistent files created with the old Tails version are present in the filesystem 1.326
And all persistent directories from the old Tails version have safe access rights 2.329
After features/support/hooks.rb:291 0.678
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:55.930
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.133
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.037
And Tor is ready 18.801
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.263
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.918
Given I shutdown Tails and wait for the computer to power off 7.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.648
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.897
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.266
When the network is plugged 0.040
And Tor is ready 16.209
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.304
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.731
Given I shutdown Tails and wait for the computer to power off 4.020
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.714
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.703
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.031
And Tor is ready 16.579
Then the Upgrader considers the system as up-to-date 0.236
# 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.565
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.877
After features/support/hooks.rb:291 0.718
After features/support/hooks.rb:75 0.025
Tags: @product @automatic_upgrade
33.202
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.240
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
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.716
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 15.296
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.579
After features/support/hooks.rb:291 0.869
After features/support/hooks.rb:75 0.000