Project Number Date
test_Tails_ISO_devel 3201 19 Dec 2023, 12:16

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:17.127 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:22.745
Before features/support/hooks.rb:245 0.007
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 18.839
When I start Tails from USB drive "old" with network unplugged 58.798
Then the boot device has safe access rights 2.907
And Tails is running from USB drive "old" 0.287
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:291 3.493
After features/support/hooks.rb:75 0.008
Tags: @product
1:56.183
Before features/support/hooks.rb:245 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:3.400
Then Tails is running from USB drive "old" 0.393
And I create a persistent partition 42.872
And I take note of which tps features are available 1.321
Then a Tails persistence partition exists on USB drive "old" 0.916
And I shutdown Tails and wait for the computer to power off 7.094
After features/support/hooks.rb:291 0.149
After features/support/hooks.rb:75 0.010
Tags: @product
2:12.417
Before features/support/hooks.rb:245 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:45.515
Then Tails is running from USB drive "old" 0.333
And all tps features are active 2.109
When I write some files expected to persist 1.734
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.647
And all persistent directories from the old Tails version have safe access rights 2.698
And I take note of which tps features are available 0.511
And I shutdown Tails and wait for the computer to power off 3.063
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.341
After features/support/hooks.rb:291 0.132
After features/support/hooks.rb:75 0.011
Tags: @product
2:30.559
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.121
And I log in to a new session 15.764
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.161
And I plug USB drive "to_upgrade" 2.388
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.276
Then the running Tails is installed on USB drive "to_upgrade" 12.475
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:291 3.502
After features/support/hooks.rb:75 0.000
Tags: @product
1:53.785
Before features/support/hooks.rb:245 0.007
Given a computer 0.214
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.823
Then all tps features from the old Tails version are active 1.665
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.550
And the expected persistent files created with the old Tails version are present in the filesystem 1.505
And all persistent directories from the old Tails version have safe access rights 2.714
After features/support/hooks.rb:291 0.724
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:54.216
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 10.525
And no SquashFS delta is installed 0.175
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.069
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.336
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.645
When the network is plugged 0.043
And Tor is ready 17.712
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.183
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.758
Given I shutdown Tails and wait for the computer to power off 5.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.357
Then Tails is running version 2.2~testoverlayfsng 0.101
And all tps features are active 2.148
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.333
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.265
# 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.283
When the network is plugged 0.045
And Tor is ready 14.361
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.608
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.611
Given I shutdown Tails and wait for the computer to power off 4.288
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.786
Then Tails is running version 2.3~testoverlayfsng 0.089
And all tps features are active 2.064
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.581
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.058
# 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.281
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.275
When the network is plugged 0.044
And Tor is ready 14.520
Then the Upgrader considers the system as up-to-date 10.749
# 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.144
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 3.094
After features/support/hooks.rb:291 0.818
After features/support/hooks.rb:75 0.024
Tags: @product @automatic_upgrade
27.220
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.755
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.348
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.073
And the signing key used by the Upgrader is outdated 1.263
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 13.087
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.646
After features/support/hooks.rb:291 0.664
After features/support/hooks.rb:75 0.000