Project Number Date
test_Tails_ISO_stable 4616 12 Jan 2024, 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 16:55.753 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.325
Before features/support/hooks.rb:245 0.005
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 22.037
When I start Tails from USB drive "old" with network unplugged 1:8.136
Then the boot device has safe access rights 2.958
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.245
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:291 3.501
After features/support/hooks.rb:75 0.024
Tags: @product
2:0.461
Before features/support/hooks.rb:245 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:3.094
Then Tails is running from USB drive "old" 0.606
And I create a persistent partition 45.000
And I take note of which tps features are available 1.573
Then a Tails persistence partition exists on USB drive "old" 0.738
And I shutdown Tails and wait for the computer to power off 9.245
After features/support/hooks.rb:291 0.143
After features/support/hooks.rb:75 0.011
Tags: @product
2:23.205
Before features/support/hooks.rb:245 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:56.534
Then Tails is running from USB drive "old" 0.392
And all tps features are active 2.201
When I write some files expected to persist 1.856
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.661
And all persistent directories from the old Tails version have safe access rights 2.881
And I take note of which tps features are available 0.400
And I shutdown Tails and wait for the computer to power off 3.076
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.769
After features/support/hooks.rb:291 0.129
After features/support/hooks.rb:75 0.007
Tags: @product
2:29.256
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.773
And I log in to a new session 16.046
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.017
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.805
Then the running Tails is installed on USB drive "to_upgrade" 12.785
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:291 7.193
After features/support/hooks.rb:75 0.000
Tags: @product
1:57.233
Before features/support/hooks.rb:245 0.006
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.173
Then all tps features from the old Tails version are active 1.705
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.344
And the expected persistent files created with the old Tails version are present in the filesystem 1.559
And all persistent directories from the old Tails version have safe access rights 2.969
After features/support/hooks.rb:291 0.773
After features/support/hooks.rb:75 0.014
Tags: @product @automatic_upgrade
5:57.409
Before features/support/hooks.rb:245 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.813
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.306
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.050
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.370
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.587
When the network is plugged 0.037
And Tor is ready 18.835
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.686
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.184
Given I shutdown Tails and wait for the computer to power off 5.221
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.846
Then Tails is running version 2.2~testoverlayfsng 0.114
And all tps features are active 2.288
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.406
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.060
# 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.326
When the network is plugged 0.042
And Tor is ready 15.159
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.605
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.252
Given I shutdown Tails and wait for the computer to power off 3.155
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.589
Then Tails is running version 2.3~testoverlayfsng 0.125
And all tps features are active 2.140
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.532
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.055
# 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.280
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.409
When the network is plugged 0.108
And Tor is ready 15.962
Then the Upgrader considers the system as up-to-date 0.272
# 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 24.814
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.324
After features/support/hooks.rb:291 0.802
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
32.859
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.066
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.307
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.552
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 17.198
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.615
After features/support/hooks.rb:291 1.111
After features/support/hooks.rb:75 0.000