Project Number Date
test_Tails_ISO_stable 4846 17 May 2024, 12:12

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:57.695 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:8.383
Before features/support/hooks.rb:259 0.007
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.401
When I start Tails from USB drive "old" with network unplugged 1:32.397
Then the boot device has safe access rights 3.210
And Tails is running from USB drive "old" 0.418
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:305 3.796
After features/support/hooks.rb:89 0.009
Tags: @product
2:15.469
Before features/support/hooks.rb:259 0.005
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:26.195
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 38.226
And I take note of which tps features are available 1.450
Then a Tails persistence partition exists on USB drive "old" 0.766
And I shutdown Tails and wait for the computer to power off 8.304
After features/support/hooks.rb:305 0.186
After features/support/hooks.rb:89 0.008
Tags: @product
2:52.574
Before features/support/hooks.rb:259 0.006
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.947
Then Tails is running from USB drive "old" 0.371
And all tps features are active 2.230
When I write some files expected to persist 1.729
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 2.594
And I take note of which tps features are available 0.391
And I shutdown Tails and wait for the computer to power off 4.214
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.348
After features/support/hooks.rb:305 0.165
After features/support/hooks.rb:89 0.010
Tags: @product
2:20.561
Before features/support/hooks.rb:259 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 9.448
And I log in to a new session 17.155
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.619
And I plug USB drive "to_upgrade" 2.502
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.961
Then the running Tails is installed on USB drive "to_upgrade" 16.516
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:305 3.564
After features/support/hooks.rb:89 0.000
Tags: @product
2:11.098
Before features/support/hooks.rb:259 0.005
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.980
Then all tps features from the old Tails version are active 1.538
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 3.438
And the expected persistent files created with the old Tails version are present in the filesystem 1.370
And all persistent directories from the old Tails version have safe access rights 2.302
After features/support/hooks.rb:305 0.693
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
7:32.116
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.544
And no SquashFS delta is installed 0.084
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.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.055
And Tor is ready 19.904
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.838
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.712
Given I shutdown Tails and wait for the computer to power off 10.804
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.760
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.131
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.361
# 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.263
When the network is plugged 0.033
And Tor is ready 45.647
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.601
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.075
Given I shutdown Tails and wait for the computer to power off 4.500
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.054
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.976
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.043
And Tor is ready 47.748
Then the Upgrader considers the system as up-to-date 0.319
# 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 15.013
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.924
After features/support/hooks.rb:305 0.887
After features/support/hooks.rb:89 0.024
Tags: @product @automatic_upgrade
37.489
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.406
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.485
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 19.339
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.877
After features/support/hooks.rb:305 0.662
After features/support/hooks.rb:89 0.000