Project Number Date
test_Tails_ISO_devel 3531 04 Oct 2024, 12:32

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:42.004 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:3.440
Before features/support/hooks.rb:269 0.006
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.283
When I start Tails from USB drive "old" with network unplugged 1:28.014
Then the boot device has safe access rights 2.870
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 7.060
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.697
Before features/support/hooks.rb:269 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:21.472
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 31.090
And I take note of which tps features are available 1.225
Then a Tails persistence partition exists on USB drive "old" 0.872
And I shutdown Tails and wait for the computer to power off 8.553
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.008
Tags: @product
2:45.751
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.655
Then Tails is running from USB drive "old" 2.090
And all tps features are active 1.933
When I write some files expected to persist 1.728
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.267
And all persistence configuration files have safe access rights 0.518
And all persistent directories from the old Tails version have safe access rights 4.299
And I take note of which tps features are available 0.383
And I shutdown Tails and wait for the computer to power off 4.308
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.374
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.016
Tags: @product
2:30.960
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.313
And I log in to a new session 19.651
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.883
And I plug USB drive "to_upgrade" 2.398
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.091
Then the running Tails is installed on USB drive "to_upgrade" 19.185
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:326 6.837
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.977
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.150
Then all tps features from the old Tails version are active 1.765
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.491
And the expected persistent files created with the old Tails version are present in the filesystem 1.488
And all persistent directories from the old Tails version have safe access rights 2.567
After features/support/hooks.rb:326 0.665
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:23.312
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 14.844
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.543
When the network is plugged 0.074
And Tor is ready 23.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.739
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.175
Given I shutdown Tails and wait for the computer to power off 10.719
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.734
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 3.803
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.279
When the network is plugged 0.073
And Tor is ready 17.151
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.464
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.252
Given I shutdown Tails and wait for the computer to power off 4.389
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.576
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.844
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.067
And Tor is ready 19.959
Then the Upgrader considers the system as up-to-date 0.342
# 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.282
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.095
After features/support/hooks.rb:326 0.721
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.863
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the signing key used by the Upgrader is outdated 0.764
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 20.749
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.632
After features/support/hooks.rb:326 0.743
After features/support/hooks.rb:100 0.000