Project Number Date
test_Tails_ISO_stable 5092 11 Sep 2024, 12:29

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:5.883 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.047
Before features/support/hooks.rb:269 0.003
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.792
When I start Tails from USB drive "old" with network unplugged 1:28.877
Then the boot device has safe access rights 3.122
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 3.550
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.402
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:26.592
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 30.955
And I take note of which tps features are available 2.107
Then a Tails persistence partition exists on USB drive "old" 0.828
And I shutdown Tails and wait for the computer to power off 8.413
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.449
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.482
Then Tails is running from USB drive "old" 0.326
And all tps features are active 2.197
When I write some files expected to persist 1.649
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.331
And all persistent directories from the old Tails version have safe access rights 2.540
And I take note of which tps features are available 0.426
And I shutdown Tails and wait for the computer to power off 4.516
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.573
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.197
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 14.972
And I log in to a new session 20.259
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.634
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.378
Then the running Tails is installed on USB drive "to_upgrade" 17.103
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 2.553
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.465
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.827
Then all tps features from the old Tails version are active 1.786
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.346
And the expected persistent files created with the old Tails version are present in the filesystem 1.541
And all persistent directories from the old Tails version have safe access rights 2.445
After features/support/hooks.rb:326 0.937
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:39.234
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 11.237
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.073
And Tor is ready 20.009
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.483
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.557
Given I shutdown Tails and wait for the computer to power off 8.995
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.708
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 2.379
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.410
# 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.282
When the network is plugged 0.091
And Tor is ready 19.784
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.929
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.500
Given I shutdown Tails and wait for the computer to power off 4.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.370
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.129
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.076
And Tor is ready 19.189
Then the Upgrader considers the system as up-to-date 0.329
# 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 13.467
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.090
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
34.086
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 9.948
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.053
And the signing key used by the Upgrader is outdated 0.759
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 16.158
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.769
After features/support/hooks.rb:326 1.184
After features/support/hooks.rb:100 0.000