Project Number Date
test_Tails_ISO_stable 4661 11 Feb 2024, 15:03

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:45.904 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.013
Before features/support/hooks.rb:245 0.006
Given a computer 0.124
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 19.248
When I start Tails from USB drive "old" with network unplugged 57.688
Then the boot device has safe access rights 3.004
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:291 3.456
After features/support/hooks.rb:75 0.010
Tags: @product
1:56.142
Before features/support/hooks.rb:245 0.006
Given a computer 0.132
And I start Tails from USB drive "old" with network unplugged and I login 1:3.726
Then Tails is running from USB drive "old" 0.444
And I create a persistent partition 42.738
And I take note of which tps features are available 1.229
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 7.062
After features/support/hooks.rb:291 0.147
After features/support/hooks.rb:75 0.010
Tags: @product
2:22.399
Before features/support/hooks.rb:245 0.005
Given a computer 0.154
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:56.763
Then Tails is running from USB drive "old" 0.312
And all tps features are active 1.809
When I write some files expected to persist 1.835
# 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.415
And all persistent directories from the old Tails version have safe access rights 2.831
And I take note of which tps features are available 0.294
And I shutdown Tails and wait for the computer to power off 3.052
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.661
After features/support/hooks.rb:291 0.136
After features/support/hooks.rb:75 0.010
Tags: @product
2:37.983
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 12.721
And I log in to a new session 18.146
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.360
And I plug USB drive "to_upgrade" 2.505
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.883
Then the running Tails is installed on USB drive "to_upgrade" 13.985
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:291 6.641
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.773
Before features/support/hooks.rb:245 0.006
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.261
Then all tps features from the old Tails version are active 1.573
And Tails is running from USB drive "to_upgrade" 0.412
And the boot device has safe access rights 3.711
And the expected persistent files created with the old Tails version are present in the filesystem 1.408
And all persistent directories from the old Tails version have safe access rights 3.245
After features/support/hooks.rb:291 0.740
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:3.287
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 12.014
And no SquashFS delta is installed 0.140
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.428
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.051
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.364
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.585
When the network is plugged 0.055
And Tor is ready 15.740
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.765
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.687
Given I shutdown Tails and wait for the computer to power off 5.351
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.351
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 1.836
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.428
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.293
When the network is plugged 0.021
And Tor is ready 13.782
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.035
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.736
Given I shutdown Tails and wait for the computer to power off 3.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.480
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 1.726
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.668
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.067
# 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.292
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.331
When the network is plugged 0.018
And Tor is ready 16.153
Then the Upgrader considers the system as up-to-date 10.724
# 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 29.794
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.344
After features/support/hooks.rb:291 0.780
After features/support/hooks.rb:75 0.054
Tags: @product @automatic_upgrade
27.304
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.245
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.496
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the signing key used by the Upgrader is outdated 0.485
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 14.132
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.858
After features/support/hooks.rb:291 0.803
After features/support/hooks.rb:75 0.000