Project Number Date
test_Tails_ISO_stable 4784 11 Apr 2024, 19:02

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 17:32.223 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:42.196
Before features/support/hooks.rb:259 0.010
Given a computer 0.237
And I create a 7200 MiB disk named "old" 0.109
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 25.533
When I start Tails from USB drive "old" with network unplugged 1:11.104
Then the boot device has safe access rights 3.018
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.270
After features/support/hooks.rb:305 7.495
After features/support/hooks.rb:89 0.034
Tags: @product
2:1.841
Before features/support/hooks.rb:259 0.039
Given a computer 0.445
And I start Tails from USB drive "old" with network unplugged and I login 1:17.106
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 33.118
And I take note of which tps features are available 1.324
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.668
After features/support/hooks.rb:305 0.165
After features/support/hooks.rb:89 0.009
Tags: @product
2:40.894
Before features/support/hooks.rb:259 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.907
Then Tails is running from USB drive "old" 0.402
And all tps features are active 2.199
When I write some files expected to persist 1.952
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.485
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.560
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.087
After features/support/hooks.rb:305 0.110
After features/support/hooks.rb:89 0.012
Tags: @product
2:21.158
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.186
And I log in to a new session 15.836
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.439
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.886
Then the running Tails is installed on USB drive "to_upgrade" 15.032
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:305 3.611
After features/support/hooks.rb:89 0.000
Tags: @product
2:5.957
Before features/support/hooks.rb:259 0.008
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.211
Then all tps features from the old Tails version are active 1.966
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.784
And the expected persistent files created with the old Tails version are present in the filesystem 1.770
And all persistent directories from the old Tails version have safe access rights 2.589
After features/support/hooks.rb:305 1.057
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:6.340
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.667
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.369
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.034
And Tor is ready 18.054
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.056
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.896
Given I shutdown Tails and wait for the computer to power off 6.898
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.202
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.427
And the file system changes introduced in version 6.2~testoverlayfs are present 0.382
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.464
# 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.264
When the network is plugged 0.045
And Tor is ready 15.219
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.441
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.063
Given I shutdown Tails and wait for the computer to power off 4.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.207
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.509
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.366
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.039
And Tor is ready 17.895
Then the Upgrader considers the system as up-to-date 0.247
# 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.102
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.081
After features/support/hooks.rb:305 0.708
After features/support/hooks.rb:89 0.023
Tags: @product @automatic_upgrade
33.833
Before features/support/hooks.rb:259 0.037
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.555
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.525
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.490
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 16.657
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.507
After features/support/hooks.rb:305 0.676
After features/support/hooks.rb:89 0.000