Project Number Date
test_Tails_ISO_stable 4598 01 Jan 2024, 12:30

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:14.335 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.694
Before features/support/hooks.rb:245 0.005
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 18.614
When I start Tails from USB drive "old" with network unplugged 1:0.851
Then the boot device has safe access rights 3.073
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.262
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:291 3.683
After features/support/hooks.rb:75 0.009
Tags: @product
1:59.192
Before features/support/hooks.rb:245 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:4.593
Then Tails is running from USB drive "old" 0.544
And I create a persistent partition 44.169
And I take note of which tps features are available 1.621
Then a Tails persistence partition exists on USB drive "old" 0.959
And I shutdown Tails and wait for the computer to power off 7.116
After features/support/hooks.rb:291 0.192
After features/support/hooks.rb:75 0.009
Tags: @product
2:19.031
Before features/support/hooks.rb:245 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.601
Then Tails is running from USB drive "old" 0.354
And all tps features are active 2.341
When I write some files expected to persist 2.240
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.591
And all persistent directories from the old Tails version have safe access rights 2.958
And I take note of which tps features are available 0.501
And I shutdown Tails and wait for the computer to power off 3.077
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.885
After features/support/hooks.rb:291 0.098
After features/support/hooks.rb:75 0.011
Tags: @product
2:33.941
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.004
And I log in to a new session 17.438
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.161
And I plug USB drive "to_upgrade" 2.500
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.159
Then the running Tails is installed on USB drive "to_upgrade" 15.278
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:291 0.757
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.664
Before features/support/hooks.rb:245 0.005
Given a computer 0.238
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.544
Then all tps features from the old Tails version are active 1.789
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 3.491
And the expected persistent files created with the old Tails version are present in the filesystem 1.495
And all persistent directories from the old Tails version have safe access rights 2.714
After features/support/hooks.rb:291 0.706
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
6:22.595
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.722
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.262
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.063
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.393
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.718
When the network is plugged 0.057
And Tor is ready 16.611
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.709
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.350
Given I shutdown Tails and wait for the computer to power off 6.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.755
Then Tails is running version 2.2~testoverlayfsng 0.148
And all tps features are active 2.214
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.365
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.286
# 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.269
When the network is plugged 0.139
And Tor is ready 15.258
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.687
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.585
Given I shutdown Tails and wait for the computer to power off 4.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.469
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 2.206
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.680
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.320
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.460
When the network is plugged 0.045
And Tor is ready 44.214
Then the Upgrader considers the system as up-to-date 0.319
# 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 26.611
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.537
After features/support/hooks.rb:291 0.760
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
30.214
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 9.425
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.298
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the signing key used by the Upgrader is outdated 1.102
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 17.562
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.698
After features/support/hooks.rb:291 0.784
After features/support/hooks.rb:75 0.000