Project Number Date
test_Tails_ISO_devel 3590 17 Nov 2024, 13:17

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 21:2.119 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:43.566
Before features/support/hooks.rb:269 0.006
Given a computer 0.238
And I create a 7200 MiB disk named "old" 0.074
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 1:5.731
When I start Tails from USB drive "old" with network unplugged 1:32.159
Then the boot device has safe access rights 3.229
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 7.889
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.013
Before features/support/hooks.rb:269 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:29.179
Then Tails is running from USB drive "old" 0.433
And I create a persistent partition 34.611
And I take note of which tps features are available 2.093
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 8.546
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.012
Tags: @product
3:13.265
Before features/support/hooks.rb:269 0.007
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.001
Then Tails is running from USB drive "old" 0.381
And all tps features are active 2.255
When I write some files expected to persist 1.901
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
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.603
And I take note of which tps features are available 0.548
And I shutdown Tails and wait for the computer to power off 4.261
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.330
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.008
Tags: @product
2:41.205
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.154
And I log in to a new session 25.217
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.645
And I plug USB drive "to_upgrade" 2.353
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.569
Then the running Tails is installed on USB drive "to_upgrade" 23.835
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.539
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.177
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.209
Then all tps features from the old Tails version are active 1.762
And Tails is running from USB drive "to_upgrade" 0.415
And the boot device has safe access rights 4.257
And the expected persistent files created with the old Tails version are present in the filesystem 1.621
And all persistent directories from the old Tails version have safe access rights 2.697
After features/support/hooks.rb:326 0.689
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:44.459
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 19.137
And no SquashFS delta is installed 0.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.640
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.461
When the network is plugged 0.077
And Tor is ready 20.317
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.830
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.029
Given I shutdown Tails and wait for the computer to power off 11.043
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.193
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.737
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.377
# 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.504
When the network is plugged 0.086
And Tor is ready 20.407
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.346
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.886
Given I shutdown Tails and wait for the computer to power off 4.736
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.716
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.240
And the file system changes introduced in version 6.3~testoverlayfs are present 0.576
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.368
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.134
And Tor is ready 17.416
Then the Upgrader considers the system as up-to-date 0.329
# 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.289
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.191
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
57.432
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 10.166
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 signing key used by the Upgrader is outdated 0.745
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 45.283
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.690
After features/support/hooks.rb:326 1.042
After features/support/hooks.rb:100 0.000