Project Number Date
test_Tails_ISO_devel 3202 20 Dec 2023, 12:36

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:52.488 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:28.978
Before features/support/hooks.rb:245 0.008
Given a computer 0.259
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 20.798
When I start Tails from USB drive "old" with network unplugged 1:2.229
Then the boot device has safe access rights 3.371
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.348
After features/support/hooks.rb:291 3.703
After features/support/hooks.rb:75 0.013
Tags: @product
2:1.484
Before features/support/hooks.rb:245 0.008
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:5.348
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 44.956
And I take note of which tps features are available 2.540
Then a Tails persistence partition exists on USB drive "old" 0.900
And I shutdown Tails and wait for the computer to power off 7.144
After features/support/hooks.rb:291 0.142
After features/support/hooks.rb:75 0.012
Tags: @product
2:26.105
Before features/support/hooks.rb:245 0.008
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:58.425
Then Tails is running from USB drive "old" 0.396
And all tps features are active 2.248
When I write some files expected to persist 1.929
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.668
And all persistent directories from the old Tails version have safe access rights 2.814
And I take note of which tps features are available 0.631
And I shutdown Tails and wait for the computer to power off 3.267
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.305
After features/support/hooks.rb:291 0.119
After features/support/hooks.rb:75 0.008
Tags: @product
2:41.890
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.209
And I log in to a new session 16.072
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.271
And I plug USB drive "to_upgrade" 2.660
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:54.662
Then the running Tails is installed on USB drive "to_upgrade" 14.583
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:291 7.172
After features/support/hooks.rb:75 0.000
Tags: @product
2:14.333
Before features/support/hooks.rb:245 0.005
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.003
Then all tps features from the old Tails version are active 1.881
And Tails is running from USB drive "to_upgrade" 0.401
And the boot device has safe access rights 4.119
And the expected persistent files created with the old Tails version are present in the filesystem 1.717
And all persistent directories from the old Tails version have safe access rights 2.992
After features/support/hooks.rb:291 0.805
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:32.096
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.494
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.271
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.082
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.436
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.571
When the network is plugged 0.050
And Tor is ready 16.966
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.695
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.204
Given I shutdown Tails and wait for the computer to power off 6.230
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.674
Then Tails is running version 2.2~testoverlayfsng 0.128
And all tps features are active 2.386
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.444
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.276
When the network is plugged 0.043
And Tor is ready 16.404
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.913
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.027
Given I shutdown Tails and wait for the computer to power off 4.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.297
Then Tails is running version 2.3~testoverlayfsng 0.103
And all tps features are active 2.086
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.647
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.075
# 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.299
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.374
When the network is plugged 0.049
And Tor is ready 42.830
Then the Upgrader considers the system as up-to-date 0.275
# 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.657
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.202
After features/support/hooks.rb:291 0.794
After features/support/hooks.rb:75 0.026
Tags: @product @automatic_upgrade
27.598
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.789
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.300
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.116
And the signing key used by the Upgrader is outdated 0.491
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 12.985
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.867
After features/support/hooks.rb:291 0.753
After features/support/hooks.rb:75 0.000