Project Number Date
test_Tails_ISO_stable 4524 23 Nov 2023, 16:56

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 19:8.366 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
2:3.477
Before features/support/hooks.rb:245 0.007
Given a computer 0.147
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 51.569
When I start Tails from USB drive "old" with network unplugged 1:6.648
Then the boot device has safe access rights 3.099
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:290 3.527
After features/support/hooks.rb:75 0.009
Tags: @product
2:3.350
Before features/support/hooks.rb:245 0.006
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:7.811
Then Tails is running from USB drive "old" 0.502
And I create a persistent partition 45.214
And I take note of which tps features are available 1.644
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 7.126
After features/support/hooks.rb:290 0.150
After features/support/hooks.rb:75 0.009
Tags: @product
2:29.926
Before features/support/hooks.rb:245 0.004
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:54.115
Then Tails is running from USB drive "old" 0.433
And all tps features are active 8.470
When I write some files expected to persist 2.156
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.400
And all persistence configuration files have safe access rights 1.232
And all persistent directories from the old Tails version have safe access rights 3.065
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 3.065
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.318
After features/support/hooks.rb:290 0.167
After features/support/hooks.rb:75 0.010
Tags: @product
3:29.490
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 26.366
And I log in to a new session 21.830
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.087
And I plug USB drive "to_upgrade" 2.595
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:10.358
Then the running Tails is installed on USB drive "to_upgrade" 25.761
And I unplug USB drive "to_upgrade" 0.255
And I unplug USB drive "__internal" 0.235
After features/support/hooks.rb:290 1.918
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.702
Before features/support/hooks.rb:245 0.006
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.208
Then all tps features from the old Tails version are active 5.669
And Tails is running from USB drive "to_upgrade" 0.408
And the boot device has safe access rights 3.736
And the expected persistent files created with the old Tails version are present in the filesystem 1.820
And all persistent directories from the old Tails version have safe access rights 2.682
After features/support/hooks.rb:290 0.654
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:26.999
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.620
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.345
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.066
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.435
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.653
When the network is plugged 0.025
And Tor is ready 16.261
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.665
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.744
Given I shutdown Tails and wait for the computer to power off 6.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.355
Then Tails is running version 2.2~testoverlayfsng 0.094
And all tps features are active 6.112
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.384
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.068
# 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.345
When the network is plugged 0.017
And Tor is ready 15.987
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.622
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.109
Given I shutdown Tails and wait for the computer to power off 4.059
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.803
Then Tails is running version 2.3~testoverlayfsng 0.118
And all tps features are active 5.925
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.657
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.127
# 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.308
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.316
When the network is plugged 0.022
And Tor is ready 43.511
Then the Upgrader considers the system as up-to-date 0.236
# 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.759
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.555
After features/support/hooks.rb:290 0.874
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
30.419
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 11.311
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.328
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.098
And the signing key used by the Upgrader is outdated 1.742
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 13.923
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.987
After features/support/hooks.rb:290 0.693
After features/support/hooks.rb:75 0.000