Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 38 23 Aug 2024, 20:23

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:23.201 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:28.130
Before features/support/hooks.rb:269 0.006
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 32.436
When I start Tails from USB drive "old" with network unplugged 1:49.818
Then the boot device has safe access rights 3.404
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 7.470
After features/support/hooks.rb:100 0.012
Tags: @product
2:15.205
Before features/support/hooks.rb:269 0.006
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:30.855
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 32.781
And I take note of which tps features are available 1.474
Then a Tails persistence partition exists on USB drive "old" 0.898
And I shutdown Tails and wait for the computer to power off 8.645
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.014
Tags: @product
3:18.998
Before features/support/hooks.rb:269 0.007
Given a computer 0.284
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.320
Then Tails is running from USB drive "old" 1.628
And all tps features are active 4.420
When I write some files expected to persist 3.042
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.379
And I take note of which tps features are available 1.449
And I shutdown Tails and wait for the computer to power off 4.664
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.191
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.012
Tags: @product
2:38.553
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.866
And I log in to a new session 20.421
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.557
And I plug USB drive "to_upgrade" 2.495
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.897
Then the running Tails is installed on USB drive "to_upgrade" 23.841
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.252
After features/support/hooks.rb:326 2.821
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.627
Before features/support/hooks.rb:269 0.010
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.420
Then all tps features from the old Tails version are active 1.806
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.217
And the expected persistent files created with the old Tails version are present in the filesystem 1.934
And all persistent directories from the old Tails version have safe access rights 2.674
After features/support/hooks.rb:326 1.073
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:41.651
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.908
And no SquashFS delta is installed 0.243
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.373
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.335
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.480
When the network is plugged 0.116
And Tor is ready 24.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.958
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.527
Given I shutdown Tails and wait for the computer to power off 11.176
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.962
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.430
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
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.343
# 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.322
When the network is plugged 0.075
And Tor is ready 20.256
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.948
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.694
Given I shutdown Tails and wait for the computer to power off 6.637
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.363
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.432
And the file system changes introduced in version 6.3~testoverlayfs are present 0.624
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.414
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.210
And Tor is ready 20.532
Then the Upgrader considers the system as up-to-date 0.363
# 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.936
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.082
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
40.033
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.836
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.668
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.209
And the signing key used by the Upgrader is outdated 0.874
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 19.138
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.191
After features/support/hooks.rb:326 0.670
After features/support/hooks.rb:100 0.000