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

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:17.922 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:58.491
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.274
When I start Tails from USB drive "old" with network unplugged 1:25.148
Then the boot device has safe access rights 2.809
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.503
After features/support/hooks.rb:100 0.029
Tags: @product
2:3.428
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:21.991
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 30.559
And I take note of which tps features are available 1.447
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.127
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.127
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.300
Then Tails is running from USB drive "old" 0.811
And all tps features are active 1.904
When I write some files expected to persist 1.786
# 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 0.412
And all persistent directories from the old Tails version have safe access rights 2.380
And I take note of which tps features are available 0.591
And I shutdown Tails and wait for the computer to power off 4.321
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.116
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.710
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.841
And I log in to a new session 22.665
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.642
And I plug USB drive "to_upgrade" 2.662
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.619
Then the running Tails is installed on USB drive "to_upgrade" 20.857
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 3.955
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.016
Before features/support/hooks.rb:269 0.005
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.434
Then all tps features from the old Tails version are active 1.740
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.288
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.612
After features/support/hooks.rb:326 1.008
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:13.339
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.496
And no SquashFS delta is installed 0.273
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.737
When the network is plugged 0.080
And Tor is ready 22.342
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.902
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.136
Given I shutdown Tails and wait for the computer to power off 10.586
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.466
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.417
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.313
When the network is plugged 0.101
And Tor is ready 19.258
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.995
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.902
Given I shutdown Tails and wait for the computer to power off 4.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.149
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.064
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.291
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.063
And Tor is ready 17.513
Then the Upgrader considers the system as up-to-date 0.295
# 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 16.172
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.092
After features/support/hooks.rb:326 0.782
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.809
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.585
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
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.064
And Tor is ready 20.203
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.913
After features/support/hooks.rb:326 0.717
After features/support/hooks.rb:100 0.000