Project Number Date
test_Tails_ISO_stable 5072 05 Sep 2024, 08:34

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:42.656 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:18.692
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.833
When I start Tails from USB drive "old" with network unplugged 1:40.166
Then the boot device has safe access rights 3.296
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.109
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:326 3.560
After features/support/hooks.rb:100 0.012
Tags: @product
2:17.197
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:33.065
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 32.605
And I take note of which tps features are available 1.548
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 8.615
After features/support/hooks.rb:326 0.179
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.998
Before features/support/hooks.rb:269 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.370
Then Tails is running from USB drive "old" 0.375
And all tps features are active 2.031
When I write some files expected to persist 1.762
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.621
And I take note of which tps features are available 0.531
And I shutdown Tails and wait for the computer to power off 4.304
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.167
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.570
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.302
And I log in to a new session 20.892
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.624
And I plug USB drive "to_upgrade" 2.373
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.620
Then the running Tails is installed on USB drive "to_upgrade" 20.342
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 3.231
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.541
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.085
Then all tps features from the old Tails version are active 1.614
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.539
And the expected persistent files created with the old Tails version are present in the filesystem 1.405
And all persistent directories from the old Tails version have safe access rights 2.373
After features/support/hooks.rb:326 0.901
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
6:48.579
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.666
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.080
And Tor is ready 52.248
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.592
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.612
Given I shutdown Tails and wait for the computer to power off 10.816
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.010
Then Tails is running version 6.2~testoverlayfs 0.031
And all tps features are active 2.207
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.273
When the network is plugged 0.069
And Tor is ready 17.096
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.477
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.972
Given I shutdown Tails and wait for the computer to power off 4.472
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.682
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.271
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.081
# 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.362
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.076
And Tor is ready 19.491
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 13.761
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.956
After features/support/hooks.rb:326 0.756
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
34.077
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.746
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.862
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 15.399
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.593
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.000