Project Number Date
test_Tails_ISO_20522-ocr-more 10 19 Dec 2024, 05:20

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:15.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
1:59.859
Before features/support/hooks.rb:269 0.005
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.356
When I start Tails from USB drive "old" with network unplugged 1:25.055
Then the boot device has safe access rights 3.086
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.233
After features/support/hooks.rb:326 6.917
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.356
Before features/support/hooks.rb:269 0.005
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:20.784
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 32.212
And I take note of which tps features are available 1.608
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.362
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.807
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.199
Then Tails is running from USB drive "old" 0.690
And all tps features are active 1.903
When I write some files expected to persist 2.345
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.231
And I take note of which tps features are available 0.413
And I shutdown Tails and wait for the computer to power off 4.181
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.007
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.688
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.139
And I log in to a new session 19.928
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.459
And I plug USB drive "to_upgrade" 5.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.798
Then the running Tails is installed on USB drive "to_upgrade" 19.763
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 3.040
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.520
Before features/support/hooks.rb:269 0.006
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.862
Then all tps features from the old Tails version are active 1.655
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 2.956
And the expected persistent files created with the old Tails version are present in the filesystem 1.307
And all persistent directories from the old Tails version have safe access rights 2.238
After features/support/hooks.rb:326 0.932
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:15.704
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.361
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.911
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.547
When the network is plugged 0.078
And Tor is ready 21.932
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.120
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.892
Given I shutdown Tails and wait for the computer to power off 10.730
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.072
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.346
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.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.434
When the network is plugged 0.073
And Tor is ready 18.642
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.053
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.874
Given I shutdown Tails and wait for the computer to power off 4.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.985
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.040
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.120
And Tor is ready 19.566
Then the Upgrader considers the system as up-to-date 0.316
# 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 15.997
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.972
After features/support/hooks.rb:326 0.856
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.060
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.407
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.434
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.902
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 17.820
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.358
After features/support/hooks.rb:326 0.681
After features/support/hooks.rb:100 0.000