Project Number Date
test_Tails_ISO_devel 3221 03 Jan 2024, 12:15

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:12.863 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:35.800
Before features/support/hooks.rb:245 0.008
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 20.183
When I start Tails from USB drive "old" with network unplugged 1:10.198
Then the boot device has safe access rights 3.168
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:291 3.532
After features/support/hooks.rb:75 0.029
Tags: @product
2:1.775
Before features/support/hooks.rb:245 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:5.714
Then Tails is running from USB drive "old" 0.473
And I create a persistent partition 44.685
And I take note of which tps features are available 1.724
Then a Tails persistence partition exists on USB drive "old" 0.875
And I shutdown Tails and wait for the computer to power off 8.099
After features/support/hooks.rb:291 0.117
After features/support/hooks.rb:75 0.013
Tags: @product
2:24.084
Before features/support/hooks.rb:245 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.070
Then Tails is running from USB drive "old" 0.437
And all tps features are active 2.275
When I write some files expected to persist 2.029
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.294
And all persistence configuration files have safe access rights 0.753
And all persistent directories from the old Tails version have safe access rights 3.233
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 3.073
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.210
After features/support/hooks.rb:291 0.131
After features/support/hooks.rb:75 0.010
Tags: @product
2:34.620
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.608
And I log in to a new session 17.398
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.337
And I plug USB drive "to_upgrade" 2.500
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.415
Then the running Tails is installed on USB drive "to_upgrade" 12.887
And I unplug USB drive "to_upgrade" 0.273
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:291 7.144
After features/support/hooks.rb:75 0.000
Tags: @product
2:6.221
Before features/support/hooks.rb:245 0.009
Given a computer 0.214
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.161
Then all tps features from the old Tails version are active 1.742
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 4.038
And the expected persistent files created with the old Tails version are present in the filesystem 1.906
And all persistent directories from the old Tails version have safe access rights 2.757
After features/support/hooks.rb:291 0.777
After features/support/hooks.rb:75 0.033
Tags: @product @automatic_upgrade
6:1.306
Before features/support/hooks.rb:245 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.343
And no SquashFS delta is installed 0.149
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.327
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.069
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.371
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.560
When the network is plugged 0.193
And Tor is ready 17.527
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.932
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.196
Given I shutdown Tails and wait for the computer to power off 6.376
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.291
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 2.395
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.378
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.415
When the network is plugged 0.037
And Tor is ready 14.635
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.804
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.866
Given I shutdown Tails and wait for the computer to power off 4.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.021
Then Tails is running version 2.3~testoverlayfsng 0.116
And all tps features are active 2.094
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.656
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.079
# 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.273
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.299
When the network is plugged 0.044
And Tor is ready 15.620
Then the Upgrader considers the system as up-to-date 0.300
# 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 27.676
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.457
After features/support/hooks.rb:291 0.855
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
29.054
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.763
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.413
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the signing key used by the Upgrader is outdated 0.591
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 16.467
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.723
After features/support/hooks.rb:291 1.307
After features/support/hooks.rb:75 0.000