Project Number Date
test_Tails_ISO_stable 4974 26 Jul 2024, 12:25

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:27.525 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:21.331
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.118
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 30.925
When I start Tails from USB drive "old" with network unplugged 1:44.743
Then the boot device has safe access rights 3.162
And Tails is running from USB drive "old" 0.425
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 3.627
After features/support/hooks.rb:100 0.012
Tags: @product
2:12.464
Before features/support/hooks.rb:269 0.013
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:26.903
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 34.041
And I take note of which tps features are available 1.798
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 8.360
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.577
Before features/support/hooks.rb:269 0.004
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.597
Then Tails is running from USB drive "old" 0.354
And all tps features are active 2.062
When I write some files expected to persist 1.946
# 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.415
And all persistent directories from the old Tails version have safe access rights 2.604
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 4.433
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.252
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.605
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 9.801
And I log in to a new session 18.744
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.136
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.122
Then the running Tails is installed on USB drive "to_upgrade" 20.897
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 1.978
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.570
Before features/support/hooks.rb:269 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.838
Then all tps features from the old Tails version are active 1.742
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.253
And the expected persistent files created with the old Tails version are present in the filesystem 1.675
And all persistent directories from the old Tails version have safe access rights 2.498
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:36.816
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 11.899
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.377
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.036
And Tor is ready 19.178
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.710
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.085
Given I shutdown Tails and wait for the computer to power off 9.010
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.171
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.358
And the file system changes introduced in version 6.2~testoverlayfs are present 0.381
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.402
# 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.327
When the network is plugged 0.039
And Tor is ready 20.444
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.996
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.217
Given I shutdown Tails and wait for the computer to power off 4.398
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.449
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.036
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.389
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.040
And Tor is ready 21.438
Then the Upgrader considers the system as up-to-date 0.308
# 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.901
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.236
After features/support/hooks.rb:326 0.842
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
37.158
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.199
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.950
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 18.656
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.914
After features/support/hooks.rb:326 0.861
After features/support/hooks.rb:100 0.000