Project Number Date
test_Tails_ISO_stable 5183 15 Oct 2024, 08:32

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:26.043 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:12.015
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 33.020
When I start Tails from USB drive "old" with network unplugged 1:33.694
Then the boot device has safe access rights 3.038
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.749
After features/support/hooks.rb:100 0.009
Tags: @product
2:2.901
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:20.676
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 31.096
And I take note of which tps features are available 1.611
Then a Tails persistence partition exists on USB drive "old" 0.852
And I shutdown Tails and wait for the computer to power off 8.160
After features/support/hooks.rb:326 0.231
After features/support/hooks.rb:100 0.007
Tags: @product
2:50.482
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.054
Then Tails is running from USB drive "old" 0.635
And all tps features are active 2.131
When I write some files expected to persist 1.767
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.273
And all persistence configuration files have safe access rights 0.597
And all persistent directories from the old Tails version have safe access rights 2.687
And I take note of which tps features are available 0.582
And I shutdown Tails and wait for the computer to power off 4.619
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.954
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.007
Tags: @product
2:47.176
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 24.290
And I log in to a new session 19.444
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.549
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.200
Then the running Tails is installed on USB drive "to_upgrade" 20.788
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.614
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.772
Before features/support/hooks.rb:269 0.007
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.070
Then all tps features from the old Tails version are active 1.652
And Tails is running from USB drive "to_upgrade" 0.408
And the boot device has safe access rights 3.517
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.417
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:21.622
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 11.994
And no SquashFS delta is installed 0.183
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
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.360
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.088
And Tor is ready 23.426
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.397
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.675
Given I shutdown Tails and wait for the computer to power off 8.828
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.584
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.282
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.438
When the network is plugged 0.085
And Tor is ready 19.631
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.297
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.464
Given I shutdown Tails and wait for the computer to power off 4.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.011
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.928
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.467
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.405
When the network is plugged 0.075
And Tor is ready 17.783
Then the Upgrader considers the system as up-to-date 0.338
# 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.623
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.809
After features/support/hooks.rb:326 0.814
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
59.073
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.666
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.375
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.739
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 47.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.597
After features/support/hooks.rb:326 0.700
After features/support/hooks.rb:100 0.000