Project Number Date
test_Tails_ISO_stable 4596 30 Dec 2023, 12:20

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:34.099 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:29.857
Before features/support/hooks.rb:245 0.005
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 21.610
When I start Tails from USB drive "old" with network unplugged 1:2.774
Then the boot device has safe access rights 3.251
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.256
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:291 3.522
After features/support/hooks.rb:75 0.012
Tags: @product
2:2.185
Before features/support/hooks.rb:245 0.008
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:9.742
Then Tails is running from USB drive "old" 0.402
And I create a persistent partition 43.531
And I take note of which tps features are available 1.352
Then a Tails persistence partition exists on USB drive "old" 0.790
And I shutdown Tails and wait for the computer to power off 6.150
After features/support/hooks.rb:291 0.113
After features/support/hooks.rb:75 0.010
Tags: @product
2:24.084
Before features/support/hooks.rb:245 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:56.313
Then Tails is running from USB drive "old" 0.323
And all tps features are active 2.173
When I write some files expected to persist 1.709
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.637
And all persistent directories from the old Tails version have safe access rights 2.727
And I take note of which tps features are available 0.514
And I shutdown Tails and wait for the computer to power off 3.072
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.185
After features/support/hooks.rb:291 0.116
After features/support/hooks.rb:75 0.009
Tags: @product
2:37.845
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 10.997
And I log in to a new session 19.787
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.442
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.971
Then the running Tails is installed on USB drive "to_upgrade" 12.744
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:291 7.509
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.210
Before features/support/hooks.rb:245 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.707
Then all tps features from the old Tails version are active 1.782
And Tails is running from USB drive "to_upgrade" 0.393
And the boot device has safe access rights 3.802
And the expected persistent files created with the old Tails version are present in the filesystem 1.554
And all persistent directories from the old Tails version have safe access rights 2.769
After features/support/hooks.rb:291 0.688
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:27.580
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 40.963
And no SquashFS delta is installed 0.152
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.298
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.098
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.403
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.605
When the network is plugged 0.051
And Tor is ready 16.993
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.852
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.627
Given I shutdown Tails and wait for the computer to power off 6.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.069
Then Tails is running version 2.2~testoverlayfsng 0.101
And all tps features are active 2.344
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.435
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.103
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.268
# 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.353
When the network is plugged 0.038
And Tor is ready 16.583
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.583
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.100
Given I shutdown Tails and wait for the computer to power off 4.089
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.175
Then Tails is running version 2.3~testoverlayfsng 0.108
And all tps features are active 2.176
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.765
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.307
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.348
When the network is plugged 0.044
And Tor is ready 15.819
Then the Upgrader considers the system as up-to-date 0.276
# 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.489
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.480
After features/support/hooks.rb:291 0.691
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
27.334
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.505
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.360
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.256
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 12.308
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.735
After features/support/hooks.rb:291 0.924
After features/support/hooks.rb:75 0.000