Project Number Date
test_Tails_ISO_devel 3261 30 Jan 2024, 17:14

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:55.744 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:39.533
Before features/support/hooks.rb:245 0.005
Given a computer 0.265
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.773
When I start Tails from USB drive "old" with network unplugged 1:2.020
Then the boot device has safe access rights 3.371
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:291 3.566
After features/support/hooks.rb:75 0.010
Tags: @product
1:59.218
Before features/support/hooks.rb:245 0.004
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:5.679
Then Tails is running from USB drive "old" 0.505
And I create a persistent partition 43.574
And I take note of which tps features are available 1.391
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 7.061
After features/support/hooks.rb:291 0.144
After features/support/hooks.rb:75 0.008
Tags: @product
2:36.196
Before features/support/hooks.rb:245 0.005
Given a computer 0.486
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.897
Then Tails is running from USB drive "old" 0.397
And all tps features are active 2.218
When I write some files expected to persist 1.878
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 2.858
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 3.217
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.052
After features/support/hooks.rb:291 0.141
After features/support/hooks.rb:75 0.010
Tags: @product
2:33.614
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.688
And I log in to a new session 16.279
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.184
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.261
Then the running Tails is installed on USB drive "to_upgrade" 13.317
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:291 2.080
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.508
Before features/support/hooks.rb:245 0.008
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.776
Then all tps features from the old Tails version are active 1.996
And Tails is running from USB drive "to_upgrade" 0.470
And the boot device has safe access rights 3.970
And the expected persistent files created with the old Tails version are present in the filesystem 2.036
And all persistent directories from the old Tails version have safe access rights 3.051
After features/support/hooks.rb:291 0.806
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:33.056
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 14.189
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.359
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.090
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.449
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.527
When the network is plugged 0.035
And Tor is ready 45.164
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.551
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.169
Given I shutdown Tails and wait for the computer to power off 6.160
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.277
Then Tails is running version 2.2~testoverlayfsng 0.113
And all tps features are active 2.439
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.371
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.349
When the network is plugged 0.030
And Tor is ready 16.081
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.893
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.186
Given I shutdown Tails and wait for the computer to power off 3.537
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.482
Then Tails is running version 2.3~testoverlayfsng 0.104
And all tps features are active 2.232
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.581
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.101
# 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.294
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.334
When the network is plugged 0.045
And Tor is ready 15.530
Then the Upgrader considers the system as up-to-date 10.787
# 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 28.015
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.983
After features/support/hooks.rb:291 1.017
After features/support/hooks.rb:75 0.036
Tags: @product @automatic_upgrade
29.617
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.682
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.333
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.067
And the signing key used by the Upgrader is outdated 1.308
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 15.452
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.718
After features/support/hooks.rb:291 1.188
After features/support/hooks.rb:75 0.000