Project Number Date
test_Tails_ISO_20522-ocr-more 43 28 Jan 2025, 05:49

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 19:23.816 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:8.685
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.136
When I start Tails from USB drive "old" with network unplugged 1:33.093
Then the boot device has safe access rights 3.178
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.489
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.133
Before features/support/hooks.rb:269 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:27.223
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 35.611
And I take note of which tps features are available 1.570
Then a Tails persistence partition exists on USB drive "old" 0.863
And I shutdown Tails and wait for the computer to power off 8.282
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.668
Before features/support/hooks.rb:269 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.604
Then Tails is running from USB drive "old" 0.650
And all tps features are active 2.107
When I write some files expected to persist 1.870
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.316
And all persistence configuration files have safe access rights 1.289
And all persistent directories from the old Tails version have safe access rights 2.623
And I take note of which tps features are available 0.481
And I shutdown Tails and wait for the computer to power off 4.275
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.241
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.926
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.566
And I log in to a new session 19.568
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.729
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.586
Then the running Tails is installed on USB drive "to_upgrade" 23.503
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.273
After features/support/hooks.rb:326 2.392
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.324
Before features/support/hooks.rb:269 0.005
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.141
Then all tps features from the old Tails version are active 1.724
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 4.070
And the expected persistent files created with the old Tails version are present in the filesystem 1.501
And all persistent directories from the old Tails version have safe access rights 4.325
After features/support/hooks.rb:326 0.896
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:26.563
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 12.152
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.851
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.552
When the network is plugged 0.078
And Tor is ready 22.292
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.871
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.492
Given I shutdown Tails and wait for the computer to power off 8.592
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.378
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.443
And the file system changes introduced in version 6.2~testoverlayfs are present 0.358
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.511
# 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.070
And Tor is ready 17.499
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.289
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.878
Given I shutdown Tails and wait for the computer to power off 4.317
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.437
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.274
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.080
And Tor is ready 20.779
Then the Upgrader considers the system as up-to-date 0.312
# 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.940
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.080
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
37.513
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 11.248
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.427
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.114
But a current signing key is available on our website 0.000
When the network is plugged 0.155
And Tor is ready 18.906
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.594
After features/support/hooks.rb:326 0.893
After features/support/hooks.rb:100 0.000