Project Number Date
test_Tails_ISO_20522-ocr-more 21 30 Dec 2024, 05:05

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:54.069 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.617
Before features/support/hooks.rb:269 0.003
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 30.247
When I start Tails from USB drive "old" with network unplugged 1:31.031
Then the boot device has safe access rights 3.025
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.094
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.700
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.239
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 1:24.427
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 30.566
And I take note of which tps features are available 1.454
Then a Tails persistence partition exists on USB drive "old" 0.746
And I shutdown Tails and wait for the computer to power off 8.478
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.953
Before features/support/hooks.rb:269 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.479
Then Tails is running from USB drive "old" 0.320
And all tps features are active 1.891
When I write some files expected to persist 1.913
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.346
And all persistent directories from the old Tails version have safe access rights 2.300
And I take note of which tps features are available 0.488
And I shutdown Tails and wait for the computer to power off 4.516
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.313
After features/support/hooks.rb:326 0.105
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.404
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 14.296
And I log in to a new session 20.494
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.588
And I plug USB drive "to_upgrade" 2.679
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.033
Then the running Tails is installed on USB drive "to_upgrade" 21.885
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 3.557
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.673
Before features/support/hooks.rb:269 0.005
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.047
Then all tps features from the old Tails version are active 1.740
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.449
And the expected persistent files created with the old Tails version are present in the filesystem 1.475
And all persistent directories from the old Tails version have safe access rights 2.378
After features/support/hooks.rb:326 1.302
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:17.457
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.771
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.527
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.490
When the network is plugged 0.066
And Tor is ready 21.682
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.585
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.482
Given I shutdown Tails and wait for the computer to power off 8.610
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.108
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.347
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.361
When the network is plugged 0.087
And Tor is ready 15.152
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.050
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.275
Given I shutdown Tails and wait for the computer to power off 6.305
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.461
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.099
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.374
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.641
When the network is plugged 0.082
And Tor is ready 18.537
Then the Upgrader considers the system as up-to-date 0.308
# 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 17.214
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.016
After features/support/hooks.rb:326 0.673
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
38.723
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 10.210
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.123
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 20.848
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.007
After features/support/hooks.rb:326 0.777
After features/support/hooks.rb:100 0.000