Project Number Date
test_Tails_ISO_stable 4626 20 Jan 2024, 12:49

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.868 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:25.033
Before features/support/hooks.rb:245 0.005
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 18.277
When I start Tails from USB drive "old" with network unplugged 1:1.703
Then the boot device has safe access rights 2.919
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:291 3.468
After features/support/hooks.rb:75 0.009
Tags: @product
1:57.260
Before features/support/hooks.rb:245 0.006
Given a computer 0.136
And I start Tails from USB drive "old" with network unplugged and I login 1:3.066
Then Tails is running from USB drive "old" 0.518
And I create a persistent partition 43.205
And I take note of which tps features are available 1.310
Then a Tails persistence partition exists on USB drive "old" 0.814
And I shutdown Tails and wait for the computer to power off 8.207
After features/support/hooks.rb:291 0.153
After features/support/hooks.rb:75 0.010
Tags: @product
2:9.523
Before features/support/hooks.rb:245 0.006
Given a computer 0.138
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.917
Then Tails is running from USB drive "old" 0.375
And all tps features are active 1.748
When I write some files expected to persist 1.869
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.585
And all persistent directories from the old Tails version have safe access rights 2.470
And I take note of which tps features are available 0.306
And I shutdown Tails and wait for the computer to power off 3.059
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.824
After features/support/hooks.rb:291 0.128
After features/support/hooks.rb:75 0.009
Tags: @product
2:29.914
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 10.177
And I log in to a new session 15.448
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.383
And I plug USB drive "to_upgrade" 2.465
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.217
Then the running Tails is installed on USB drive "to_upgrade" 12.730
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.288
After features/support/hooks.rb:291 1.975
After features/support/hooks.rb:75 0.000
Tags: @product
2:2.997
Before features/support/hooks.rb:245 0.005
Given a computer 0.136
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.825
Then all tps features from the old Tails version are active 1.391
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.787
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 2.812
After features/support/hooks.rb:291 0.735
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
6:12.863
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.982
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.295
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.057
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.496
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.530
When the network is plugged 0.019
And Tor is ready 17.409
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.683
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.923
Given I shutdown Tails and wait for the computer to power off 5.248
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.737
Then Tails is running version 2.2~testoverlayfsng 0.115
And all tps features are active 1.781
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.438
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.286
# 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.258
When the network is plugged 0.032
And Tor is ready 42.108
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.520
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.486
Given I shutdown Tails and wait for the computer to power off 4.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.612
Then Tails is running version 2.3~testoverlayfsng 0.110
And all tps features are active 1.669
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.536
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.061
# 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.280
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.270
When the network is plugged 0.021
And Tor is ready 16.458
Then the Upgrader considers the system as up-to-date 0.243
# 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 27.429
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.269
After features/support/hooks.rb:291 0.716
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
28.275
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.451
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.323
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.047
And the signing key used by the Upgrader is outdated 1.250
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 14.564
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.607
After features/support/hooks.rb:291 0.670
After features/support/hooks.rb:75 0.000