Project Number Date
test_Tails_ISO_stable 4683 27 Feb 2024, 21:16

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:37.959 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:30.507
Before features/support/hooks.rb:245 0.006
Given a computer 0.162
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 20.649
When I start Tails from USB drive "old" with network unplugged 1:4.718
Then the boot device has safe access rights 2.922
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:291 3.503
After features/support/hooks.rb:75 0.053
Tags: @product
2:6.480
Before features/support/hooks.rb:245 0.006
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:12.116
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 43.557
And I take note of which tps features are available 1.501
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 8.025
After features/support/hooks.rb:291 0.157
After features/support/hooks.rb:75 0.010
Tags: @product
2:37.362
Before features/support/hooks.rb:245 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.544
Then Tails is running from USB drive "old" 0.375
And all tps features are active 1.770
When I write some files expected to persist 1.502
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.346
And all persistent directories from the old Tails version have safe access rights 2.277
And I take note of which tps features are available 0.282
And I shutdown Tails and wait for the computer to power off 4.033
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.833
After features/support/hooks.rb:291 0.096
After features/support/hooks.rb:75 0.010
Tags: @product
2:29.332
Before features/support/hooks.rb:245 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 10.164
And I log in to a new session 15.666
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.420
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.544
Then the running Tails is installed on USB drive "to_upgrade" 14.704
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:291 1.928
After features/support/hooks.rb:75 0.000
Tags: @product
2:21.631
Before features/support/hooks.rb:245 0.007
Given a computer 0.157
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.860
Then all tps features from the old Tails version are active 3.818
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 3.019
And the expected persistent files created with the old Tails version are present in the filesystem 1.419
And all persistent directories from the old Tails version have safe access rights 3.050
After features/support/hooks.rb:291 0.826
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:57.445
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.766
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
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.460
When the network is plugged 0.038
And Tor is ready 20.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.371
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.884
Given I shutdown Tails and wait for the computer to power off 6.127
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.625
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.849
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.283
# 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.308
When the network is plugged 0.029
And Tor is ready 18.073
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.334
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.389
Given I shutdown Tails and wait for the computer to power off 5.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.605
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.683
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.288
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.035
And Tor is ready 19.429
Then the Upgrader considers the system as up-to-date 0.274
# 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.051
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.933
After features/support/hooks.rb:291 0.765
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
35.200
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.935
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.687
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 17.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.599
After features/support/hooks.rb:291 0.672
After features/support/hooks.rb:75 0.000