Project Number Date
test_Tails_ISO_devel 3233 12 Jan 2024, 12:32

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.854 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:58.863
Before features/support/hooks.rb:245 0.007
Given a computer 0.298
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 37.990
When I start Tails from USB drive "old" with network unplugged 1:14.956
Then the boot device has safe access rights 3.459
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.262
After features/support/hooks.rb:291 3.580
After features/support/hooks.rb:75 0.011
Tags: @product
2:2.007
Before features/support/hooks.rb:245 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:6.547
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 44.425
And I take note of which tps features are available 1.495
Then a Tails persistence partition exists on USB drive "old" 0.863
And I shutdown Tails and wait for the computer to power off 8.122
After features/support/hooks.rb:291 0.152
After features/support/hooks.rb:75 0.011
Tags: @product
2:28.228
Before features/support/hooks.rb:245 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.523
Then Tails is running from USB drive "old" 0.450
And all tps features are active 2.250
When I write some files expected to persist 2.124
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.331
And all persistence configuration files have safe access rights 0.613
And all persistent directories from the old Tails version have safe access rights 2.689
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 3.160
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.422
After features/support/hooks.rb:291 0.109
After features/support/hooks.rb:75 0.009
Tags: @product
2:30.197
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.808
And I log in to a new session 17.297
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.186
And I plug USB drive "to_upgrade" 2.461
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.229
Then the running Tails is installed on USB drive "to_upgrade" 12.823
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:291 1.755
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.820
Before features/support/hooks.rb:245 0.008
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.181
Then all tps features from the old Tails version are active 1.778
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.600
And the expected persistent files created with the old Tails version are present in the filesystem 1.757
And all persistent directories from the old Tails version have safe access rights 2.993
After features/support/hooks.rb:291 0.754
After features/support/hooks.rb:75 0.035
Tags: @product @automatic_upgrade
5:50.211
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.792
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.400
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.064
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.354
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.567
When the network is plugged 0.051
And Tor is ready 14.882
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.815
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.835
Given I shutdown Tails and wait for the computer to power off 6.412
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.287
Then Tails is running version 2.2~testoverlayfsng 0.111
And all tps features are active 5.598
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.412
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.269
# 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.476
When the network is plugged 0.049
And Tor is ready 17.612
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.844
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.247
Given I shutdown Tails and wait for the computer to power off 4.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.863
Then Tails is running version 2.3~testoverlayfsng 0.108
And all tps features are active 2.191
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.604
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.082
# 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.306
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.269
When the network is plugged 0.068
And Tor is ready 17.990
Then the Upgrader considers the system as up-to-date 0.290
# 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 25.683
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.259
After features/support/hooks.rb:291 0.763
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
26.526
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.684
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.449
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.050
And the signing key used by the Upgrader is outdated 0.439
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 14.252
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.605
After features/support/hooks.rb:291 1.155
After features/support/hooks.rb:75 0.000