Project Number Date
test_Tails_ISO_stable 4655 07 Feb 2024, 22:01

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 16:26.234 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:24.760
Before features/support/hooks.rb:245 0.005
Given a computer 0.130
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 20.261
When I start Tails from USB drive "old" with network unplugged 59.349
Then the boot device has safe access rights 3.077
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.255
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:291 4.456
After features/support/hooks.rb:75 0.008
Tags: @product
1:56.754
Before features/support/hooks.rb:245 0.005
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:4.578
Then Tails is running from USB drive "old" 0.389
And I create a persistent partition 42.429
And I take note of which tps features are available 1.227
Then a Tails persistence partition exists on USB drive "old" 0.838
And I shutdown Tails and wait for the computer to power off 7.086
After features/support/hooks.rb:291 0.200
After features/support/hooks.rb:75 0.011
Tags: @product
2:19.108
Before features/support/hooks.rb:245 0.006
Given a computer 0.481
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:52.243
Then Tails is running from USB drive "old" 0.346
And all tps features are active 1.740
When I write some files expected to persist 1.780
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
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.679
And I take note of which tps features are available 0.331
And I shutdown Tails and wait for the computer to power off 3.064
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.813
After features/support/hooks.rb:291 0.106
After features/support/hooks.rb:75 0.010
Tags: @product
2:29.075
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 10.618
And I log in to a new session 15.098
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.304
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.558
Then the running Tails is installed on USB drive "to_upgrade" 11.670
And I unplug USB drive "to_upgrade" 0.181
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:291 0.874
After features/support/hooks.rb:75 0.000
Tags: @product
2:14.076
Before features/support/hooks.rb:245 0.005
Given a computer 0.135
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.911
Then all tps features from the old Tails version are active 1.425
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.362
And the expected persistent files created with the old Tails version are present in the filesystem 1.704
And all persistent directories from the old Tails version have safe access rights 3.219
After features/support/hooks.rb:291 0.651
After features/support/hooks.rb:75 0.030
Tags: @product @automatic_upgrade
5:35.039
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.208
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.324
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.086
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.408
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.715
When the network is plugged 0.027
And Tor is ready 15.659
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.754
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.904
Given I shutdown Tails and wait for the computer to power off 5.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.599
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 1.733
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.466
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.382
When the network is plugged 0.022
And Tor is ready 15.303
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.631
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.828
Given I shutdown Tails and wait for the computer to power off 4.076
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.015
Then Tails is running version 2.3~testoverlayfsng 0.094
And all tps features are active 1.715
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.560
And only the 2.3~testoverlayfsng 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.308
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.270
When the network is plugged 0.021
And Tor is ready 18.280
Then the Upgrader considers the system as up-to-date 0.349
# 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 24.999
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.352
After features/support/hooks.rb:291 0.761
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
27.418
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.324
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.379
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.058
And the signing key used by the Upgrader is outdated 0.460
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 14.407
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.758
After features/support/hooks.rb:291 0.917
After features/support/hooks.rb:75 0.000