Project Number Date
test_Tails_ISO_devel 3474 11 Aug 2024, 12:59

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:44.540 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:5.333
Before features/support/hooks.rb:269 0.008
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.071
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.384
When I start Tails from USB drive "old" with network unplugged 1:31.667
Then the boot device has safe access rights 2.905
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 3.762
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.267
Before features/support/hooks.rb:269 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:22.485
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 30.051
And I take note of which tps features are available 1.936
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.447
After features/support/hooks.rb:326 0.243
After features/support/hooks.rb:100 0.010
Tags: @product
2:56.332
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.382
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.211
When I write some files expected to persist 1.792
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.466
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 4.388
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.322
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.304
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.281
And I log in to a new session 18.066
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.486
And I plug USB drive "to_upgrade" 2.449
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.494
Then the running Tails is installed on USB drive "to_upgrade" 21.111
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 1.767
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.093
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.940
Then all tps features from the old Tails version are active 1.526
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.147
And the expected persistent files created with the old Tails version are present in the filesystem 1.548
And all persistent directories from the old Tails version have safe access rights 2.395
After features/support/hooks.rb:326 0.776
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:21.150
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.065
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.463
When the network is plugged 0.071
And Tor is ready 20.373
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.742
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.172
Given I shutdown Tails and wait for the computer to power off 8.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.337
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.141
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.297
When the network is plugged 0.066
And Tor is ready 16.892
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.520
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.288
Given I shutdown Tails and wait for the computer to power off 6.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.054
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 1.897
And the file system changes introduced in version 6.3~testoverlayfs are present 0.528
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.072
And Tor is ready 20.966
Then the Upgrader considers the system as up-to-date 0.334
# 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.410
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.046
After features/support/hooks.rb:326 0.863
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
34.058
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the signing key used by the Upgrader is outdated 0.879
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 17.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.294
After features/support/hooks.rb:326 0.816
After features/support/hooks.rb:100 0.000