Project Number Date
test_Tails_ISO_devel 3199 18 Dec 2023, 14:48

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 18:43.669 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.043
Before features/support/hooks.rb:245 0.005
Given a computer 0.153
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 17.899
When I start Tails from USB drive "old" with network unplugged 1:0.495
Then the boot device has safe access rights 3.335
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.103
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.285
After features/support/hooks.rb:291 3.546
After features/support/hooks.rb:75 0.011
Tags: @product
2:0.139
Before features/support/hooks.rb:245 0.007
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:6.432
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 43.720
And I take note of which tps features are available 1.304
Then a Tails persistence partition exists on USB drive "old" 0.977
And I shutdown Tails and wait for the computer to power off 7.154
After features/support/hooks.rb:291 0.150
After features/support/hooks.rb:75 0.012
Tags: @product
2:24.308
Before features/support/hooks.rb:245 0.006
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.724
Then Tails is running from USB drive "old" 0.383
And all tps features are active 2.172
When I write some files expected to persist 1.887
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.640
And all persistent directories from the old Tails version have safe access rights 3.000
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 3.057
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.563
After features/support/hooks.rb:291 0.114
After features/support/hooks.rb:75 0.010
Tags: @product
3:4.185
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 36.304
And I log in to a new session 15.049
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.448
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:53.571
Then the running Tails is installed on USB drive "to_upgrade" 14.945
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:291 6.857
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.637
Before features/support/hooks.rb:245 0.009
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.841
Then all tps features from the old Tails version are active 1.839
And Tails is running from USB drive "to_upgrade" 0.382
And the boot device has safe access rights 3.712
And the expected persistent files created with the old Tails version are present in the filesystem 1.660
And all persistent directories from the old Tails version have safe access rights 2.979
After features/support/hooks.rb:291 0.926
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
7:1.156
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 58.157
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.285
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.128
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.447
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.560
When the network is plugged 0.084
And Tor is ready 17.817
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.906
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 12.688
Given I shutdown Tails and wait for the computer to power off 6.426
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.888
Then Tails is running version 2.2~testoverlayfsng 0.124
And all tps features are active 2.550
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.414
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.358
# 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.507
When the network is plugged 0.045
And Tor is ready 18.704
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.913
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.207
Given I shutdown Tails and wait for the computer to power off 4.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.399
Then Tails is running version 2.3~testoverlayfsng 0.157
And all tps features are active 4.592
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.601
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.088
# 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.335
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.297
When the network is plugged 0.038
And Tor is ready 15.006
Then the Upgrader considers the system as up-to-date 0.264
# 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 31.215
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.711
After features/support/hooks.rb:291 0.827
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
44.198
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 22.322
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.416
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.066
And the signing key used by the Upgrader is outdated 1.456
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 16.828
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.062
After features/support/hooks.rb:291 1.027
After features/support/hooks.rb:75 0.000