Project Number Date
test_Tails_ISO_stable 5142 04 Oct 2024, 08:53

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 20:20.246 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:20.471
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 34.721
When I start Tails from USB drive "old" with network unplugged 1:39.682
Then the boot device has safe access rights 3.618
And Tails is running from USB drive "old" 0.408
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:326 3.952
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.845
Before features/support/hooks.rb:269 0.007
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:26.275
Then Tails is running from USB drive "old" 0.385
And I create a persistent partition 31.815
And I take note of which tps features are available 2.112
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 9.088
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.074
Before features/support/hooks.rb:269 0.004
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.470
Then Tails is running from USB drive "old" 1.799
And all tps features are active 2.246
When I write some files expected to persist 3.116
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.965
And all persistence configuration files have safe access rights 0.568
And all persistent directories from the old Tails version have safe access rights 2.745
And I take note of which tps features are available 0.521
And I shutdown Tails and wait for the computer to power off 4.672
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.742
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.012
Tags: @product
2:32.458
Before features/support/hooks.rb:269 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 11.749
And I log in to a new session 18.478
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.769
And I plug USB drive "to_upgrade" 2.443
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.776
Then the running Tails is installed on USB drive "to_upgrade" 19.805
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 2.338
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.467
Before features/support/hooks.rb:269 0.011
Given a computer 0.233
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.580
Then all tps features from the old Tails version are active 1.876
And Tails is running from USB drive "to_upgrade" 0.474
And the boot device has safe access rights 3.857
And the expected persistent files created with the old Tails version are present in the filesystem 1.713
And all persistent directories from the old Tails version have safe access rights 2.730
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:12.706
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.394
And no SquashFS delta is installed 0.211
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.495
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.081
And Tor is ready 23.282
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.526
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.362
Given I shutdown Tails and wait for the computer to power off 13.832
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.982
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.304
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.314
When the network is plugged 0.067
And Tor is ready 19.064
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.811
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.474
Given I shutdown Tails and wait for the computer to power off 4.840
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.741
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.113
And the file system changes introduced in version 6.3~testoverlayfs are present 0.588
And only the 6.3~testoverlayfs SquashFS delta is installed 0.108
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.075
And Tor is ready 47.840
Then the Upgrader considers the system as up-to-date 0.310
# 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.483
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.149
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
41.222
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.402
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.832
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.769
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 21.686
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.386
After features/support/hooks.rb:326 0.708
After features/support/hooks.rb:100 0.000