Project Number Date
test_Tails_ISO_stable 4608 09 Jan 2024, 12:05

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:10.356 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:30.665
Before features/support/hooks.rb:245 0.005
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 17.712
When I start Tails from USB drive "old" with network unplugged 1:7.848
Then the boot device has safe access rights 2.959
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.246
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:291 3.684
After features/support/hooks.rb:75 0.010
Tags: @product
1:54.098
Before features/support/hooks.rb:245 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:2.264
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 42.711
And I take note of which tps features are available 1.482
Then a Tails persistence partition exists on USB drive "old" 0.913
And I shutdown Tails and wait for the computer to power off 6.144
After features/support/hooks.rb:291 0.103
After features/support/hooks.rb:75 0.009
Tags: @product
2:14.591
Before features/support/hooks.rb:245 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:47.752
Then Tails is running from USB drive "old" 0.345
And all tps features are active 1.995
When I write some files expected to persist 1.710
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.574
And all persistent directories from the old Tails version have safe access rights 2.498
And I take note of which tps features are available 0.447
And I shutdown Tails and wait for the computer to power off 4.136
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.702
After features/support/hooks.rb:291 0.141
After features/support/hooks.rb:75 0.009
Tags: @product
2:29.705
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.764
And I log in to a new session 15.943
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.039
And I plug USB drive "to_upgrade" 2.449
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.656
Then the running Tails is installed on USB drive "to_upgrade" 12.473
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:291 0.910
After features/support/hooks.rb:75 0.000
Tags: @product
1:55.560
Before features/support/hooks.rb:245 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.375
Then all tps features from the old Tails version are active 1.677
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.631
And the expected persistent files created with the old Tails version are present in the filesystem 1.617
And all persistent directories from the old Tails version have safe access rights 2.693
After features/support/hooks.rb:291 0.710
After features/support/hooks.rb:75 0.007
Tags: @product @automatic_upgrade
5:37.963
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.060
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.358
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.050
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.379
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.495
When the network is plugged 0.053
And Tor is ready 14.626
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.830
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.337
Given I shutdown Tails and wait for the computer to power off 6.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.645
Then Tails is running version 2.2~testoverlayfsng 0.116
And all tps features are active 2.254
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.375
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.308
When the network is plugged 0.044
And Tor is ready 18.647
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.702
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.624
Given I shutdown Tails and wait for the computer to power off 4.113
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.952
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 2.069
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.619
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.076
# 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.278
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.266
When the network is plugged 0.046
And Tor is ready 15.621
Then the Upgrader considers the system as up-to-date 0.277
# 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 24.356
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.466
After features/support/hooks.rb:291 0.759
After features/support/hooks.rb:75 0.061
Tags: @product @automatic_upgrade
27.771
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 10.026
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.393
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.062
And the signing key used by the Upgrader is outdated 0.917
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 13.787
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.544
After features/support/hooks.rb:291 0.620
After features/support/hooks.rb:75 0.000