Project Number Date
test_Tails_ISO_devel 3255 27 Jan 2024, 12:18

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:52.579 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:20.341
Before features/support/hooks.rb:245 0.006
Given a computer 0.146
And I create a 7200 MiB disk named "old" 0.027
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 18.671
When I start Tails from USB drive "old" with network unplugged 56.505
Then the boot device has safe access rights 3.013
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:291 3.457
After features/support/hooks.rb:75 0.008
Tags: @product
1:53.414
Before features/support/hooks.rb:245 0.006
Given a computer 0.137
And I start Tails from USB drive "old" with network unplugged and I login 1:2.695
Then Tails is running from USB drive "old" 0.454
And I create a persistent partition 41.081
And I take note of which tps features are available 1.233
Then a Tails persistence partition exists on USB drive "old" 0.753
And I shutdown Tails and wait for the computer to power off 7.057
After features/support/hooks.rb:291 0.153
After features/support/hooks.rb:75 0.008
Tags: @product
2:26.305
Before features/support/hooks.rb:245 0.006
Given a computer 0.140
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:1.305
Then Tails is running from USB drive "old" 0.342
And all tps features are active 1.587
When I write some files expected to persist 1.712
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.514
And I take note of which tps features are available 0.288
And I shutdown Tails and wait for the computer to power off 3.066
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.672
After features/support/hooks.rb:291 0.095
After features/support/hooks.rb:75 0.010
Tags: @product
2:29.543
Before features/support/hooks.rb:245 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 9.625
And I log in to a new session 14.810
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.243
And I plug USB drive "to_upgrade" 2.519
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.802
Then the running Tails is installed on USB drive "to_upgrade" 12.132
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:291 0.802
After features/support/hooks.rb:75 0.000
Tags: @product
2:1.382
Before features/support/hooks.rb:245 0.007
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.552
Then all tps features from the old Tails version are active 1.565
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.454
And the expected persistent files created with the old Tails version are present in the filesystem 1.776
And all persistent directories from the old Tails version have safe access rights 2.513
After features/support/hooks.rb:291 0.653
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
6:12.942
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.850
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.380
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.476
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.535
When the network is plugged 0.022
And Tor is ready 16.727
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.652
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.274
Given I shutdown Tails and wait for the computer to power off 6.252
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.688
Then Tails is running version 2.2~testoverlayfsng 0.121
And all tps features are active 1.698
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.356
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.244
When the network is plugged 0.022
And Tor is ready 15.996
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.709
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.036
Given I shutdown Tails and wait for the computer to power off 4.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.262
Then Tails is running version 2.3~testoverlayfsng 0.095
And all tps features are active 1.784
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.628
And only the 2.3~testoverlayfsng 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.285
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.298
When the network is plugged 0.025
And Tor is ready 42.871
Then the Upgrader considers the system as up-to-date 0.290
# 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 25.829
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.678
After features/support/hooks.rb:291 0.652
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
28.648
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.148
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.417
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.099
And the signing key used by the Upgrader is outdated 0.864
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 15.505
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.580
After features/support/hooks.rb:291 0.771
After features/support/hooks.rb:75 0.000