Project Number Date
test_Tails_ISO_devel 3529 03 Oct 2024, 12:56

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:17.605 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:10.593
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.420
When I start Tails from USB drive "old" with network unplugged 1:34.509
Then the boot device has safe access rights 3.317
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 7.076
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.943
Before features/support/hooks.rb:269 0.006
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 1:24.864
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 32.860
And I take note of which tps features are available 1.627
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.205
After features/support/hooks.rb:326 0.197
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.268
Before features/support/hooks.rb:269 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.413
Then Tails is running from USB drive "old" 0.975
And all tps features are active 2.057
When I write some files expected to persist 1.611
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 2.614
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 4.183
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.995
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.958
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.037
And I log in to a new session 21.809
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.579
And I plug USB drive "to_upgrade" 2.398
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.849
Then the running Tails is installed on USB drive "to_upgrade" 20.885
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 2.266
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.258
Before features/support/hooks.rb:269 0.008
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.353
Then all tps features from the old Tails version are active 1.807
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.436
And the expected persistent files created with the old Tails version are present in the filesystem 1.670
And all persistent directories from the old Tails version have safe access rights 2.427
After features/support/hooks.rb:326 0.761
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:32.610
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 13.432
And no SquashFS delta is installed 0.308
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.092
And Tor is ready 22.608
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.653
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.427
Given I shutdown Tails and wait for the computer to power off 10.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.322
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.840
And the file system changes introduced in version 6.2~testoverlayfs are present 0.338
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.357
# 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.268
When the network is plugged 0.063
And Tor is ready 18.126
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.498
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.849
Given I shutdown Tails and wait for the computer to power off 6.590
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.572
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.192
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.346
When the network is plugged 0.078
And Tor is ready 19.192
Then the Upgrader considers the system as up-to-date 0.302
# 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.135
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.193
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.971
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.619
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
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.743
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 19.643
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.436
After features/support/hooks.rb:326 0.658
After features/support/hooks.rb:100 0.000