Project Number Date
test_Tails_ISO_stable 4995 03 Aug 2024, 12:40

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 18:38.722 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:11.044
Before features/support/hooks.rb:269 0.005
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.263
When I start Tails from USB drive "old" with network unplugged 1:33.521
Then the boot device has safe access rights 2.944
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.100
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 7.012
After features/support/hooks.rb:100 0.016
Tags: @product
2:13.875
Before features/support/hooks.rb:269 0.024
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:29.066
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 33.249
And I take note of which tps features are available 1.908
Then a Tails persistence partition exists on USB drive "old" 0.773
And I shutdown Tails and wait for the computer to power off 8.368
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.812
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.302
Then Tails is running from USB drive "old" 0.333
And all tps features are active 1.996
When I write some files expected to persist 1.704
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.310
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.494
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 4.301
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.235
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.147
Before features/support/hooks.rb:269 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.717
And I log in to a new session 18.236
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.815
And I plug USB drive "to_upgrade" 2.347
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.296
Then the running Tails is installed on USB drive "to_upgrade" 17.305
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 4.607
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.435
Before features/support/hooks.rb:269 0.007
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.072
Then all tps features from the old Tails version are active 1.638
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.142
And the expected persistent files created with the old Tails version are present in the filesystem 1.602
And all persistent directories from the old Tails version have safe access rights 2.460
After features/support/hooks.rb:326 0.589
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:13.852
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.155
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.454
When the network is plugged 0.044
And Tor is ready 17.823
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.726
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.102
Given I shutdown Tails and wait for the computer to power off 8.570
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.223
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.451
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.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 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.056
And Tor is ready 18.699
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.447
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.645
Given I shutdown Tails and wait for the computer to power off 4.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.021
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.939
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.346
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.062
And Tor is ready 17.644
Then the Upgrader considers the system as up-to-date 0.346
# 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 13.925
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.019
After features/support/hooks.rb:326 0.865
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
35.554
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.715
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.959
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 18.184
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.237
After features/support/hooks.rb:326 1.269
After features/support/hooks.rb:100 0.000