Project Number Date
test_Tails_ISO_stable 4849 20 May 2024, 13:03

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:43.457 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:7.918
Before features/support/hooks.rb:259 0.006
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.139
When I start Tails from USB drive "old" with network unplugged 1:33.663
Then the boot device has safe access rights 2.864
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:305 3.745
After features/support/hooks.rb:89 0.009
Tags: @product
2:11.545
Before features/support/hooks.rb:259 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:23.937
Then Tails is running from USB drive "old" 0.295
And I create a persistent partition 36.008
And I take note of which tps features are available 1.611
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 8.691
After features/support/hooks.rb:305 0.163
After features/support/hooks.rb:89 0.009
Tags: @product
2:45.251
Before features/support/hooks.rb:259 0.006
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.114
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.193
When I write some files expected to persist 1.676
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.569
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 4.342
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.740
After features/support/hooks.rb:305 0.156
After features/support/hooks.rb:89 0.010
Tags: @product
2:26.422
Before features/support/hooks.rb:259 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 10.415
And I log in to a new session 17.717
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.347
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.923
Then the running Tails is installed on USB drive "to_upgrade" 17.130
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:305 2.758
After features/support/hooks.rb:89 0.000
Tags: @product
2:13.154
Before features/support/hooks.rb:259 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.592
Then all tps features from the old Tails version are active 1.844
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 3.422
And the expected persistent files created with the old Tails version are present in the filesystem 1.447
And all persistent directories from the old Tails version have safe access rights 2.359
After features/support/hooks.rb:305 0.640
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
6:22.430
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.211
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
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.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.059
And Tor is ready 19.766
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.627
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.601
Given I shutdown Tails and wait for the computer to power off 8.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.969
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.250
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.283
When the network is plugged 0.050
And Tor is ready 16.297
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.842
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.434
Given I shutdown Tails and wait for the computer to power off 4.264
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.417
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.777
And the file system changes introduced in version 6.3~testoverlayfs are present 0.695
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.047
And Tor is ready 18.992
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 15.255
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.955
After features/support/hooks.rb:305 0.754
After features/support/hooks.rb:89 0.069
Tags: @product @automatic_upgrade
36.734
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.515
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.547
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 19.347
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.889
After features/support/hooks.rb:305 1.276
After features/support/hooks.rb:89 0.000