Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 26 17 Aug 2024, 16:31

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:11.998 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:6.294
Before features/support/hooks.rb:269 0.008
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.680
When I start Tails from USB drive "old" with network unplugged 1:31.308
Then the boot device has safe access rights 3.089
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.542
After features/support/hooks.rb:100 0.012
Tags: @product
2:4.019
Before features/support/hooks.rb:269 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:21.249
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 31.578
And I take note of which tps features are available 1.500
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 8.377
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.834
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.065
Then Tails is running from USB drive "old" 0.834
And all tps features are active 1.859
When I write some files expected to persist 1.694
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.531
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.290
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.282
After features/support/hooks.rb:326 0.095
After features/support/hooks.rb:100 0.010
Tags: @product
2:24.628
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.905
And I log in to a new session 17.746
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.502
And I plug USB drive "to_upgrade" 2.347
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.093
Then the running Tails is installed on USB drive "to_upgrade" 17.614
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 2.515
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.364
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.184
Then all tps features from the old Tails version are active 1.508
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.145
And the expected persistent files created with the old Tails version are present in the filesystem 1.349
And all persistent directories from the old Tails version have safe access rights 2.646
After features/support/hooks.rb:326 0.833
After features/support/hooks.rb:100 0.010
6:7.354
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 12.166
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.469
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.071
And Tor is ready 18.839
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.470
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.798
Given I shutdown Tails and wait for the computer to power off 8.465
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.036
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.200
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.297
When the network is plugged 0.082
And Tor is ready 17.776
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.357
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.788
Given I shutdown Tails and wait for the computer to power off 4.261
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.860
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.181
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.073
And Tor is ready 19.332
Then the Upgrader considers the system as up-to-date 0.317
# 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.483
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.256
After features/support/hooks.rb:326 0.756
After features/support/hooks.rb:100 0.020
34.502
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.962
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 1.016
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 16.697
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.332
After features/support/hooks.rb:326 0.940
After features/support/hooks.rb:100 0.000