Project Number Date
test_Tails_ISO_stable 4663 13 Feb 2024, 17: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:19.257 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:26.813
Before features/support/hooks.rb:245 0.008
Given a computer 0.462
And I create a 7200 MiB disk named "old" 0.178
And I plug USB drive "old" 1.120
And I write an old version of the Tails USB image to disk "old" 21.298
When I start Tails from USB drive "old" with network unplugged 59.708
Then the boot device has safe access rights 3.155
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.267
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:291 3.494
After features/support/hooks.rb:75 0.011
Tags: @product
1:57.432
Before features/support/hooks.rb:245 0.007
Given a computer 0.130
And I start Tails from USB drive "old" with network unplugged and I login 1:3.934
Then Tails is running from USB drive "old" 0.606
And I create a persistent partition 43.291
And I take note of which tps features are available 1.370
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 7.211
After features/support/hooks.rb:291 0.126
After features/support/hooks.rb:75 0.009
Tags: @product
2:17.729
Before features/support/hooks.rb:245 0.006
Given a computer 0.157
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.538
Then Tails is running from USB drive "old" 0.344
And all tps features are active 1.873
When I write some files expected to persist 1.633
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.504
And I take note of which tps features are available 0.688
And I shutdown Tails and wait for the computer to power off 3.074
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.250
After features/support/hooks.rb:291 0.155
After features/support/hooks.rb:75 0.011
Tags: @product
2:32.002
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 9.804
And I log in to a new session 15.309
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.169
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.573
Then the running Tails is installed on USB drive "to_upgrade" 13.345
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:291 1.005
After features/support/hooks.rb:75 0.000
Tags: @product
2:7.664
Before features/support/hooks.rb:245 0.007
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.203
Then all tps features from the old Tails version are active 1.610
And Tails is running from USB drive "to_upgrade" 0.412
And the boot device has safe access rights 3.712
And the expected persistent files created with the old Tails version are present in the filesystem 1.920
And all persistent directories from the old Tails version have safe access rights 2.635
After features/support/hooks.rb:291 0.618
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:29.803
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.039
And no SquashFS delta is installed 0.168
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.322
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.040
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.450
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.641
When the network is plugged 0.021
And Tor is ready 45.024
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.572
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.498
Given I shutdown Tails and wait for the computer to power off 5.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.125
Then Tails is running version 2.2~testoverlayfsng 0.173
And all tps features are active 2.045
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.530
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.438
When the network is plugged 0.034
And Tor is ready 16.859
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.167
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.538
Given I shutdown Tails and wait for the computer to power off 4.330
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.927
Then Tails is running version 2.3~testoverlayfsng 0.169
And all tps features are active 2.046
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.779
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.106
# 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.368
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.373
When the network is plugged 0.044
And Tor is ready 19.129
Then the Upgrader considers the system as up-to-date 0.292
# 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 28.624
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.416
After features/support/hooks.rb:291 0.810
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
27.811
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 9.543
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.357
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.055
And the signing key used by the Upgrader is outdated 0.650
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 13.502
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.654
After features/support/hooks.rb:291 0.752
After features/support/hooks.rb:75 0.000