Project Number Date
test_Tails_ISO_20522-ocr-more 27 05 Jan 2025, 05:04

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:35.438 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.706
Before features/support/hooks.rb:269 0.002
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 30.080
When I start Tails from USB drive "old" with network unplugged 1:33.496
Then the boot device has safe access rights 2.885
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.617
After features/support/hooks.rb:100 0.061
Tags: @product
2:15.252
Before features/support/hooks.rb:269 0.004
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:33.703
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 30.499
And I take note of which tps features are available 1.436
Then a Tails persistence partition exists on USB drive "old" 0.764
And I shutdown Tails and wait for the computer to power off 8.353
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.007
Tags: @product
2:53.125
Before features/support/hooks.rb:269 0.003
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.783
Then Tails is running from USB drive "old" 0.340
And all tps features are active 1.920
When I write some files expected to persist 1.697
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.537
And all persistent directories from the old Tails version have safe access rights 3.237
And I take note of which tps features are available 0.520
And I shutdown Tails and wait for the computer to power off 4.334
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.348
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.006
Tags: @product
2:37.659
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.231
And I log in to a new session 24.638
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.858
And I plug USB drive "to_upgrade" 4.125
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.515
Then the running Tails is installed on USB drive "to_upgrade" 21.869
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 3.555
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.685
Before features/support/hooks.rb:269 0.003
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.216
Then all tps features from the old Tails version are active 1.777
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.509
And the expected persistent files created with the old Tails version are present in the filesystem 1.386
And all persistent directories from the old Tails version have safe access rights 2.286
After features/support/hooks.rb:326 1.274
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
6:51.381
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.092
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.356
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.196
And Tor is ready 23.125
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.982
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.978
Given I shutdown Tails and wait for the computer to power off 10.759
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.845
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.368
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.113
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.280
When the network is plugged 0.077
And Tor is ready 19.811
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.224
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.340
Given I shutdown Tails and wait for the computer to power off 4.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.453
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.261
And the file system changes introduced in version 6.3~testoverlayfs are present 0.572
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.503
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.398
When the network is plugged 0.064
And Tor is ready 16.305
Then the Upgrader considers the system as up-to-date 10.840
# 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.331
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.961
After features/support/hooks.rb:326 1.114
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.627
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 10.525
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.430
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 19.241
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.168
After features/support/hooks.rb:326 0.646
After features/support/hooks.rb:100 0.000