Project Number Date
test_Tails_ISO_stable 4847 18 May 2024, 13:14

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:14.356 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.098
Before features/support/hooks.rb:259 0.005
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 30.116
When I start Tails from USB drive "old" with network unplugged 1:19.879
Then the boot device has safe access rights 2.869
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:305 3.477
After features/support/hooks.rb:89 0.009
Tags: @product
2:5.044
Before features/support/hooks.rb:259 0.006
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:19.445
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 34.408
And I take note of which tps features are available 1.435
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 8.531
After features/support/hooks.rb:305 0.120
After features/support/hooks.rb:89 0.012
Tags: @product
2:40.964
Before features/support/hooks.rb:259 0.005
Given a computer 0.157
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.888
Then Tails is running from USB drive "old" 0.397
And all tps features are active 1.812
When I write some files expected to persist 1.699
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.419
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 4.327
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.148
After features/support/hooks.rb:305 0.102
After features/support/hooks.rb:89 0.009
Tags: @product
2:21.065
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.994
And I log in to a new session 18.142
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.363
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.681
Then the running Tails is installed on USB drive "to_upgrade" 16.071
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:305 6.687
After features/support/hooks.rb:89 0.000
Tags: @product
2:8.997
Before features/support/hooks.rb:259 0.006
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.784
Then all tps features from the old Tails version are active 1.551
And Tails is running from USB drive "to_upgrade" 0.373
And the boot device has safe access rights 3.253
And the expected persistent files created with the old Tails version are present in the filesystem 1.559
And all persistent directories from the old Tails version have safe access rights 2.305
After features/support/hooks.rb:305 0.734
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
6:6.403
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 10.198
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.032
And Tor is ready 17.703
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.200
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.055
Given I shutdown Tails and wait for the computer to power off 8.628
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.880
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.079
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.255
When the network is plugged 0.048
And Tor is ready 17.650
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.221
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.671
Given I shutdown Tails and wait for the computer to power off 4.288
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.040
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.848
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.031
And Tor is ready 19.159
Then the Upgrader considers the system as up-to-date 0.326
# 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.155
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.845
After features/support/hooks.rb:305 0.722
After features/support/hooks.rb:89 0.018
Tags: @product @automatic_upgrade
56.782
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 9.524
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.450
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 45.891
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.565
After features/support/hooks.rb:305 0.678
After features/support/hooks.rb:89 0.000