Project Number Date
test_Tails_ISO_devel 3655 20 Jan 2025, 17:55

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 21:0.850 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:6.192
Before features/support/hooks.rb:269 0.003
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.747
When I start Tails from USB drive "old" with network unplugged 1:30.022
Then the boot device has safe access rights 3.093
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 7.846
After features/support/hooks.rb:100 0.006
Tags: @product
2:33.479
Before features/support/hooks.rb:269 0.002
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:39.358
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 42.332
And I take note of which tps features are available 2.069
Then a Tails persistence partition exists on USB drive "old" 0.804
And I shutdown Tails and wait for the computer to power off 8.343
After features/support/hooks.rb:326 0.242
After features/support/hooks.rb:100 0.005
Tags: @product
2:57.876
Before features/support/hooks.rb:269 0.002
Given a computer 0.266
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.283
Then Tails is running from USB drive "old" 0.385
And all tps features are active 2.496
When I write some files expected to persist 2.143
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.434
And all persistence configuration files have safe access rights 0.498
And all persistent directories from the old Tails version have safe access rights 3.246
And I take note of which tps features are available 2.224
And I shutdown Tails and wait for the computer to power off 4.491
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.405
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.006
Tags: @product
2:43.883
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.367
And I log in to a new session 23.889
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.660
And I plug USB drive "to_upgrade" 2.477
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.366
Then the running Tails is installed on USB drive "to_upgrade" 22.605
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.272
After features/support/hooks.rb:326 3.933
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.693
Before features/support/hooks.rb:269 0.003
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.788
Then all tps features from the old Tails version are active 1.944
And Tails is running from USB drive "to_upgrade" 0.382
And the boot device has safe access rights 3.528
And the expected persistent files created with the old Tails version are present in the filesystem 2.070
And all persistent directories from the old Tails version have safe access rights 2.762
After features/support/hooks.rb:326 0.882
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
7:38.224
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 28.379
And no SquashFS delta is installed 0.496
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.421
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.084
And Tor is ready 21.474
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.268
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.000
Given I shutdown Tails and wait for the computer to power off 13.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.483
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.797
And the file system changes introduced in version 6.2~testoverlayfs are present 0.387
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.527
# 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.370
When the network is plugged 0.104
And Tor is ready 19.749
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.450
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.386
Given I shutdown Tails and wait for the computer to power off 4.488
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.890
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.142
And the file system changes introduced in version 6.3~testoverlayfs are present 0.549
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.073
And Tor is ready 48.467
Then the Upgrader considers the system as up-to-date 0.378
# 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.996
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.268
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.046
Tags: @product @automatic_upgrade
38.500
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.286
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.650
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 19.613
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.726
After features/support/hooks.rb:326 0.714
After features/support/hooks.rb:100 0.000