Project Number Date
test_Tails_ISO_stable 5187 16 Oct 2024, 17:55

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:16.943 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:27.979
Before features/support/hooks.rb:269 0.003
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 37.542
When I start Tails from USB drive "old" with network unplugged 1:45.067
Then the boot device has safe access rights 3.090
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 9.275
After features/support/hooks.rb:100 0.007
Tags: @product
2:20.021
Before features/support/hooks.rb:269 0.004
Given a computer 0.586
And I start Tails from USB drive "old" with network unplugged and I login 1:35.875
Then Tails is running from USB drive "old" 0.392
And I create a persistent partition 32.351
And I take note of which tps features are available 1.602
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.430
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.007
Tags: @product
3:1.092
Before features/support/hooks.rb:269 0.004
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.792
Then Tails is running from USB drive "old" 0.397
And all tps features are active 2.325
When I write some files expected to persist 1.911
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.403
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.622
And I shutdown Tails and wait for the computer to power off 4.532
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.144
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.012
Tags: @product
2:38.584
Before features/support/hooks.rb:269 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 15.129
And I log in to a new session 23.136
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.830
And I plug USB drive "to_upgrade" 2.531
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.949
Then the running Tails is installed on USB drive "to_upgrade" 18.531
And I unplug USB drive "to_upgrade" 0.256
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 3.840
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.072
Before features/support/hooks.rb:269 0.007
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.983
Then all tps features from the old Tails version are active 1.842
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.749
And the expected persistent files created with the old Tails version are present in the filesystem 2.018
And all persistent directories from the old Tails version have safe access rights 2.889
After features/support/hooks.rb:326 0.827
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:48.481
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.109
And no SquashFS delta is installed 0.323
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.116
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.506
When the network is plugged 0.072
And Tor is ready 22.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.598
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.013
Given I shutdown Tails and wait for the computer to power off 11.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.475
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.296
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# 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.386
When the network is plugged 0.078
And Tor is ready 19.722
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.597
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.233
Given I shutdown Tails and wait for the computer to power off 6.672
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.267
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.228
And the file system changes introduced in version 6.3~testoverlayfs are present 0.573
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.311
When the network is plugged 0.083
And Tor is ready 20.340
Then the Upgrader considers the system as up-to-date 0.352
# 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 16.234
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.304
After features/support/hooks.rb:326 0.821
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.711
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 10.916
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 1.601
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 18.891
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.820
After features/support/hooks.rb:326 0.657
After features/support/hooks.rb:100 0.000