Project Number Date
test_Tails_ISO_devel 3666 28 Jan 2025, 09:09

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 20:48.661 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:25.348
Before features/support/hooks.rb:269 0.002
Given a computer 0.154
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 31.509
When I start Tails from USB drive "old" with network unplugged 1:48.362
Then the boot device has safe access rights 3.140
And Tails is running from USB drive "old" 0.394
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.582
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.511
Before features/support/hooks.rb:269 0.005
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login 1:30.273
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 34.023
And I take note of which tps features are available 1.933
Then a Tails persistence partition exists on USB drive "old" 1.001
And I shutdown Tails and wait for the computer to power off 8.632
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.700
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:20.895
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.224
When I write some files expected to persist 2.125
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.343
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.644
And I take note of which tps features are available 0.482
And I shutdown Tails and wait for the computer to power off 4.182
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.773
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.005
Tags: @product
2:40.031
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.679
And I log in to a new session 26.106
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.629
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.645
Then the running Tails is installed on USB drive "to_upgrade" 24.002
And I unplug USB drive "to_upgrade" 0.255
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 3.609
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.762
Before features/support/hooks.rb:269 0.003
Given a computer 0.159
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.785
Then all tps features from the old Tails version are active 1.772
And Tails is running from USB drive "to_upgrade" 0.477
And the boot device has safe access rights 3.593
And the expected persistent files created with the old Tails version are present in the filesystem 1.557
And all persistent directories from the old Tails version have safe access rights 2.416
After features/support/hooks.rb:326 0.657
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
7:15.985
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.305
And no SquashFS delta is installed 0.231
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.521
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.077
And Tor is ready 24.644
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.679
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.817
Given I shutdown Tails and wait for the computer to power off 8.743
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.033
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.429
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.293
When the network is plugged 0.066
And Tor is ready 45.085
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.642
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.220
Given I shutdown Tails and wait for the computer to power off 4.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.275
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.091
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.076
And Tor is ready 19.876
Then the Upgrader considers the system as up-to-date 0.340
# 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.210
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.135
After features/support/hooks.rb:326 0.974
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
53.322
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.542
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.524
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.111
And Tor is ready 20.828
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.166
After features/support/hooks.rb:326 1.177
After features/support/hooks.rb:100 0.000