Project Number Date
test_Tails_ISO_20522-ocr-more 18 27 Dec 2024, 05:27

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:20.218 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:10.913
Before features/support/hooks.rb:269 0.005
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.088
And I write an old version of the Tails USB image to disk "old" 32.025
When I start Tails from USB drive "old" with network unplugged 1:33.425
Then the boot device has safe access rights 3.049
And Tails is running from USB drive "old" 0.340
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.309
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:326 7.100
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.938
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:34.260
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 33.370
And I take note of which tps features are available 1.660
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 6.331
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.472
Before features/support/hooks.rb:269 0.010
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.081
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.977
When I write some files expected to persist 2.006
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 2.389
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 4.401
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.967
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.839
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 11.141
And I log in to a new session 21.385
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.761
And I plug USB drive "to_upgrade" 3.858
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.020
Then the running Tails is installed on USB drive "to_upgrade" 23.237
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 2.739
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.140
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.649
Then all tps features from the old Tails version are active 1.800
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.220
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.440
After features/support/hooks.rb:326 1.244
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:27.077
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 15.419
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.077
And Tor is ready 19.837
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.177
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.578
Given I shutdown Tails and wait for the computer to power off 11.225
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.666
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.301
And the file system changes introduced in version 6.2~testoverlayfs are present 0.431
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.355
# 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.476
When the network is plugged 0.066
And Tor is ready 18.790
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.550
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.042
Given I shutdown Tails and wait for the computer to power off 6.476
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.194
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.208
And the file system changes introduced in version 6.3~testoverlayfs are present 0.552
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.372
When the network is plugged 0.069
And Tor is ready 19.381
Then the Upgrader considers the system as up-to-date 0.370
# 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.339
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.147
After features/support/hooks.rb:326 0.777
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
39.836
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.374
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.438
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.108
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 20.240
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.549
After features/support/hooks.rb:326 0.702
After features/support/hooks.rb:100 0.000