Project Number Date
test_Tails_ISO_stable 4917 30 Jun 2024, 12:45

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:42.468 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:32.362
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.603
When I start Tails from USB drive "old" with network unplugged 1:57.625
Then the boot device has safe access rights 2.870
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 6.875
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.813
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:21.705
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 31.197
And I take note of which tps features are available 1.331
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 8.266
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.714
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.329
Then Tails is running from USB drive "old" 0.304
And all tps features are active 2.422
When I write some files expected to persist 1.621
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.453
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.356
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.992
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.007
Tags: @product
2:22.246
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.271
And I log in to a new session 15.748
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.415
And I plug USB drive "to_upgrade" 2.382
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.270
Then the running Tails is installed on USB drive "to_upgrade" 18.742
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:326 1.765
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.699
Before features/support/hooks.rb:269 0.007
Given a computer 0.271
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.499
Then all tps features from the old Tails version are active 1.539
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.175
And the expected persistent files created with the old Tails version are present in the filesystem 1.492
And all persistent directories from the old Tails version have safe access rights 2.414
After features/support/hooks.rb:326 0.654
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:6.710
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 11.014
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.042
And Tor is ready 20.472
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.060
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.597
Given I shutdown Tails and wait for the computer to power off 8.606
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.289
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.088
And the file system changes introduced in version 6.2~testoverlayfs are present 0.380
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.429
# 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.286
When the network is plugged 0.034
And Tor is ready 16.947
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.077
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.601
Given I shutdown Tails and wait for the computer to power off 4.275
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.114
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.955
And the file system changes introduced in version 6.3~testoverlayfs are present 0.426
And only the 6.3~testoverlayfs 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.044
And Tor is ready 17.505
Then the Upgrader considers the system as up-to-date 10.876
# 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 14.744
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.860
After features/support/hooks.rb:326 0.708
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
33.921
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 9.409
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 1.103
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 17.935
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.138
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.000