Project Number Date
test_Tails_ISO_devel 3217 30 Dec 2023, 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 16:39.150 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:28.177
Before features/support/hooks.rb:245 0.006
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 20.366
When I start Tails from USB drive "old" with network unplugged 1:2.369
Then the boot device has safe access rights 3.185
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:291 3.830
After features/support/hooks.rb:75 0.012
Tags: @product
1:57.255
Before features/support/hooks.rb:245 0.008
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:2.114
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 45.163
And I take note of which tps features are available 1.397
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 7.082
After features/support/hooks.rb:291 0.129
After features/support/hooks.rb:75 0.037
Tags: @product
2:26.519
Before features/support/hooks.rb:245 0.008
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:57.120
Then Tails is running from USB drive "old" 0.396
And all tps features are active 2.032
When I write some files expected to persist 1.925
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.690
And all persistent directories from the old Tails version have safe access rights 2.868
And I take note of which tps features are available 0.545
And I shutdown Tails and wait for the computer to power off 4.071
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.353
After features/support/hooks.rb:291 0.150
After features/support/hooks.rb:75 0.009
Tags: @product
2:33.604
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.491
And I log in to a new session 15.860
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.272
And I plug USB drive "to_upgrade" 2.504
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.367
Then the running Tails is installed on USB drive "to_upgrade" 13.725
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:291 0.834
After features/support/hooks.rb:75 0.000
Tags: @product
1:58.664
Before features/support/hooks.rb:245 0.007
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.283
Then all tps features from the old Tails version are active 1.734
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 3.463
And the expected persistent files created with the old Tails version are present in the filesystem 1.700
And all persistent directories from the old Tails version have safe access rights 2.913
After features/support/hooks.rb:291 0.636
After features/support/hooks.rb:75 0.043
Tags: @product @automatic_upgrade
5:48.332
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.596
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.328
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.039
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.399
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.601
When the network is plugged 0.035
And Tor is ready 19.700
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.681
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.143
Given I shutdown Tails and wait for the computer to power off 6.245
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.977
Then Tails is running version 2.2~testoverlayfsng 0.112
And all tps features are active 2.276
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.364
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.288
# 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.285
When the network is plugged 0.039
And Tor is ready 17.973
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.595
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.404
Given I shutdown Tails and wait for the computer to power off 3.142
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.953
Then Tails is running version 2.3~testoverlayfsng 0.126
And all tps features are active 2.219
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.639
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.080
# 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.276
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.282
When the network is plugged 0.050
And Tor is ready 16.363
Then the Upgrader considers the system as up-to-date 0.585
# 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 26.809
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.534
After features/support/hooks.rb:291 0.836
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
26.597
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 9.085
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.351
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.063
And the signing key used by the Upgrader is outdated 1.240
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 13.142
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.626
After features/support/hooks.rb:291 0.683
After features/support/hooks.rb:75 0.000