Project Number Date
test_Tails_ISO_devel 3190 12 Dec 2023, 12:15

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.372 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:24.685
Before features/support/hooks.rb:245 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 19.535
When I start Tails from USB drive "old" with network unplugged 59.805
Then the boot device has safe access rights 3.120
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:291 3.496
After features/support/hooks.rb:75 0.009
Tags: @product
1:56.816
Before features/support/hooks.rb:245 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:2.322
Then Tails is running from USB drive "old" 0.438
And I create a persistent partition 43.590
And I take note of which tps features are available 1.333
Then a Tails persistence partition exists on USB drive "old" 0.849
And I shutdown Tails and wait for the computer to power off 8.073
After features/support/hooks.rb:291 0.131
After features/support/hooks.rb:75 0.011
Tags: @product
2:22.605
Before features/support/hooks.rb:245 0.007
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:49.914
Then Tails is running from USB drive "old" 0.338
And all tps features are active 6.056
When I write some files expected to persist 2.129
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.308
And all persistence configuration files have safe access rights 0.650
And all persistent directories from the old Tails version have safe access rights 2.654
And I take note of which tps features are available 0.579
And I shutdown Tails and wait for the computer to power off 3.107
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.670
After features/support/hooks.rb:291 0.152
After features/support/hooks.rb:75 0.012
Tags: @product
2:38.609
Before features/support/hooks.rb:245 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.960
And I log in to a new session 17.151
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.358
And I plug USB drive "to_upgrade" 2.530
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.720
Then the running Tails is installed on USB drive "to_upgrade" 15.512
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:291 3.576
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.411
Before features/support/hooks.rb:245 0.007
Given a computer 0.314
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.286
Then all tps features from the old Tails version are active 1.605
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.553
And the expected persistent files created with the old Tails version are present in the filesystem 1.416
And all persistent directories from the old Tails version have safe access rights 2.864
After features/support/hooks.rb:291 0.694
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:9.633
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.410
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.300
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.367
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.655
When the network is plugged 0.048
And Tor is ready 14.764
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.690
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.738
Given I shutdown Tails and wait for the computer to power off 5.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.885
Then Tails is running version 2.2~testoverlayfsng 0.113
And all tps features are active 2.314
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.392
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.081
# 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.283
When the network is plugged 0.032
And Tor is ready 42.476
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.581
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.883
Given I shutdown Tails and wait for the computer to power off 3.124
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.302
Then Tails is running version 2.3~testoverlayfsng 0.116
And all tps features are active 2.271
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.630
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.069
# 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.267
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.285
When the network is plugged 0.050
And Tor is ready 12.827
Then the Upgrader considers the system as up-to-date 10.761
# 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.700
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.528
After features/support/hooks.rb:291 0.787
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
26.611
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.399
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.377
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.113
And the signing key used by the Upgrader is outdated 0.496
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 14.474
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.716
After features/support/hooks.rb:291 0.904
After features/support/hooks.rb:75 0.000