Project Number Date
test_Tails_ISO_devel 3544 11 Oct 2024, 02:58

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:31.825 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:27.135
Before features/support/hooks.rb:269 0.007
Given a computer 0.291
And I create a 7200 MiB disk named "old" 0.083
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 40.300
When I start Tails from USB drive "old" with network unplugged 1:41.072
Then the boot device has safe access rights 3.308
And Tails is running from USB drive "old" 0.288
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.576
After features/support/hooks.rb:100 0.021
Tags: @product
2:4.817
Before features/support/hooks.rb:269 0.006
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 1:21.325
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 32.223
And I take note of which tps features are available 1.384
Then a Tails persistence partition exists on USB drive "old" 0.823
And I shutdown Tails and wait for the computer to power off 8.445
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.718
Before features/support/hooks.rb:269 0.006
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.251
Then Tails is running from USB drive "old" 1.115
And all tps features are active 2.086
When I write some files expected to persist 2.471
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 2.318
And I take note of which tps features are available 1.016
And I shutdown Tails and wait for the computer to power off 4.083
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.460
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.011
Tags: @product
2:40.077
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.560
And I log in to a new session 27.908
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.484
And I plug USB drive "to_upgrade" 2.529
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.958
Then the running Tails is installed on USB drive "to_upgrade" 18.193
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.710
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.898
Before features/support/hooks.rb:269 0.006
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.747
Then all tps features from the old Tails version are active 1.662
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 3.312
And the expected persistent files created with the old Tails version are present in the filesystem 1.520
And all persistent directories from the old Tails version have safe access rights 3.098
After features/support/hooks.rb:326 1.062
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:29.827
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.197
And no SquashFS delta is installed 0.154
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
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.354
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.066
And Tor is ready 21.294
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.108
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.770
Given I shutdown Tails and wait for the computer to power off 11.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.041
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.431
And the file system changes introduced in version 6.2~testoverlayfs are present 0.366
And only the 6.2~testoverlayfs SquashFS delta is installed 0.098
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.421
When the network is plugged 0.100
And Tor is ready 21.480
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.154
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.341
Given I shutdown Tails and wait for the computer to power off 4.237
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.229
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.293
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.071
# 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.280
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.074
And Tor is ready 18.618
Then the Upgrader considers the system as up-to-date 0.344
# 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.963
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.952
After features/support/hooks.rb:326 0.679
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.351
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 9.649
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.863
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 17.434
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.834
After features/support/hooks.rb:326 0.641
After features/support/hooks.rb:100 0.000