Project Number Date
test_Tails_ISO_stable 4962 23 Jul 2024, 08:49

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:40.235 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:49.425
Before features/support/hooks.rb:269 0.015
Given a computer 1.111
And I create a 7200 MiB disk named "old" 0.290
And I plug USB drive "old" 1.080
And I write an old version of the Tails USB image to disk "old" 54.473
When I start Tails from USB drive "old" with network unplugged 1:48.184
Then the boot device has safe access rights 3.124
And Tails is running from USB drive "old" 0.403
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:326 7.279
After features/support/hooks.rb:100 0.013
Tags: @product
2:14.684
Before features/support/hooks.rb:269 0.007
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 1:29.239
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 32.785
And I take note of which tps features are available 2.076
Then a Tails persistence partition exists on USB drive "old" 1.308
And I shutdown Tails and wait for the computer to power off 8.710
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.011
Tags: @product
2:56.509
Before features/support/hooks.rb:269 0.009
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.912
Then Tails is running from USB drive "old" 0.350
And all tps features are active 2.083
When I write some files expected to persist 1.851
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.376
And all persistence configuration files have safe access rights 0.464
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.494
And I shutdown Tails and wait for the computer to power off 4.444
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.819
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.981
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.692
And I log in to a new session 21.119
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.440
And I plug USB drive "to_upgrade" 2.410
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.922
Then the running Tails is installed on USB drive "to_upgrade" 17.986
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 2.804
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.946
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.877
Then all tps features from the old Tails version are active 2.069
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 4.018
And the expected persistent files created with the old Tails version are present in the filesystem 1.695
And all persistent directories from the old Tails version have safe access rights 2.740
After features/support/hooks.rb:326 1.241
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:59.529
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 11.777
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.520
When the network is plugged 0.068
And Tor is ready 48.754
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.595
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.787
Given I shutdown Tails and wait for the computer to power off 8.703
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.193
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 4.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
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.316
# 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.274
When the network is plugged 0.178
And Tor is ready 21.279
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.301
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.872
Given I shutdown Tails and wait for the computer to power off 6.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.485
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.063
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.032
And Tor is ready 19.719
Then the Upgrader considers the system as up-to-date 0.316
# 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.861
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.340
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.158
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.791
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.978
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 21.414
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.563
After features/support/hooks.rb:326 0.958
After features/support/hooks.rb:100 0.000