Project Number Date
test_Tails_ISO_devel 3380 08 May 2024, 15:00

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:32.775 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
1:55.915
Before features/support/hooks.rb:259 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.323
When I start Tails from USB drive "old" with network unplugged 1:21.291
Then the boot device has safe access rights 3.038
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:305 3.609
After features/support/hooks.rb:89 0.011
Tags: @product
2:14.254
Before features/support/hooks.rb:259 0.007
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:22.729
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 40.099
And I take note of which tps features are available 1.501
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 8.572
After features/support/hooks.rb:305 0.214
After features/support/hooks.rb:89 0.009
Tags: @product
3:6.014
Before features/support/hooks.rb:259 0.008
Given a computer 0.335
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.384
Then Tails is running from USB drive "old" 0.392
And all tps features are active 2.055
When I write some files expected to persist 2.504
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.324
And all persistence configuration files have safe access rights 0.578
And all persistent directories from the old Tails version have safe access rights 2.558
And I take note of which tps features are available 0.400
And I shutdown Tails and wait for the computer to power off 4.497
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.982
After features/support/hooks.rb:305 0.120
After features/support/hooks.rb:89 0.011
Tags: @product
2:28.315
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 12.559
And I log in to a new session 18.528
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.587
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.565
Then the running Tails is installed on USB drive "to_upgrade" 17.157
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:305 2.397
After features/support/hooks.rb:89 0.000
Tags: @product
2:15.559
Before features/support/hooks.rb:259 0.006
Given a computer 0.291
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.967
Then all tps features from the old Tails version are active 1.588
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.267
And the expected persistent files created with the old Tails version are present in the filesystem 1.756
And all persistent directories from the old Tails version have safe access rights 2.380
After features/support/hooks.rb:305 0.576
After features/support/hooks.rb:89 0.013
Tags: @product @automatic_upgrade
6:58.601
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.794
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.035
And Tor is ready 19.685
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.531
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.869
Given I shutdown Tails and wait for the computer to power off 9.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.376
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.057
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.289
When the network is plugged 0.037
And Tor is ready 50.139
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.596
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.629
Given I shutdown Tails and wait for the computer to power off 4.435
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.579
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.957
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.242
And Tor is ready 19.142
Then the Upgrader considers the system as up-to-date 0.289
# 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.745
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.937
After features/support/hooks.rb:305 0.863
After features/support/hooks.rb:89 0.022
Tags: @product @automatic_upgrade
34.115
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.195
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.498
But a current signing key is available on our website 0.000
When the network is plugged 0.185
And Tor is ready 15.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.867
After features/support/hooks.rb:305 0.781
After features/support/hooks.rb:89 0.000