Project Number Date
test_Tails_ISO_stable 4872 04 Jun 2024, 20:39

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:15.911 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:12.943
Before features/support/hooks.rb:269 0.007
Given a computer 0.263
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.327
When I start Tails from USB drive "old" with network unplugged 1:35.854
Then the boot device has safe access rights 3.278
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.233
After features/support/hooks.rb:315 6.951
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.146
Before features/support/hooks.rb:269 0.008
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login 1:35.857
Then Tails is running from USB drive "old" 0.384
And I create a persistent partition 37.322
And I take note of which tps features are available 1.836
Then a Tails persistence partition exists on USB drive "old" 0.890
And I shutdown Tails and wait for the computer to power off 8.612
After features/support/hooks.rb:315 0.200
After features/support/hooks.rb:100 0.012
Tags: @product
2:54.151
Before features/support/hooks.rb:269 0.008
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.643
Then Tails is running from USB drive "old" 0.357
And all tps features are active 2.258
When I write some files expected to persist 2.119
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.556
And all persistent directories from the old Tails version have safe access rights 2.647
And I take note of which tps features are available 0.422
And I shutdown Tails and wait for the computer to power off 4.450
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.209
After features/support/hooks.rb:315 0.146
After features/support/hooks.rb:100 0.014
Tags: @product
2:39.073
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.301
And I log in to a new session 21.118
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.425
And I plug USB drive "to_upgrade" 2.569
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.823
Then the running Tails is installed on USB drive "to_upgrade" 21.039
And I unplug USB drive "to_upgrade" 0.444
And I unplug USB drive "__internal" 0.350
After features/support/hooks.rb:315 1.963
After features/support/hooks.rb:100 0.000
Tags: @product
2:39.658
Before features/support/hooks.rb:269 0.006
Given a computer 2.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:28.402
Then all tps features from the old Tails version are active 1.673
And Tails is running from USB drive "to_upgrade" 0.272
And the boot device has safe access rights 3.477
And the expected persistent files created with the old Tails version are present in the filesystem 1.368
And all persistent directories from the old Tails version have safe access rights 2.383
After features/support/hooks.rb:315 0.644
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:47.856
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 28.227
And no SquashFS delta is installed 0.081
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.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.373
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.042
And Tor is ready 22.149
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.039
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.423
Given I shutdown Tails and wait for the computer to power off 8.596
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.789
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.602
And the file system changes introduced in version 6.2~testoverlayfs are present 0.350
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.351
# 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.293
When the network is plugged 0.032
And Tor is ready 19.397
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.944
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.395
Given I shutdown Tails and wait for the computer to power off 4.192
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.145
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.000
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.068
# 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.435
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.424
When the network is plugged 0.037
And Tor is ready 17.907
Then the Upgrader considers the system as up-to-date 0.331
# 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.954
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.905
After features/support/hooks.rb:315 0.674
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
37.081
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.805
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 1.126
But a current signing key is available on our website 0.000
When the network is plugged 0.059
And Tor is ready 19.117
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.577
After features/support/hooks.rb:315 0.660
After features/support/hooks.rb:100 0.000