Project Number Date
test_Tails_ISO_stable 5102 19 Sep 2024, 08:35

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:8.065 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:19.603
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 31.642
When I start Tails from USB drive "old" with network unplugged 1:42.351
Then the boot device has safe access rights 3.207
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:326 7.265
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.983
Before features/support/hooks.rb:269 0.007
Given a computer 0.281
And I start Tails from USB drive "old" with network unplugged and I login 1:26.191
Then Tails is running from USB drive "old" 0.363
And I create a persistent partition 32.901
And I take note of which tps features are available 1.837
Then a Tails persistence partition exists on USB drive "old" 0.920
And I shutdown Tails and wait for the computer to power off 8.487
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.733
Before features/support/hooks.rb:269 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.219
Then Tails is running from USB drive "old" 0.378
And all tps features are active 2.148
When I write some files expected to persist 1.838
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.698
And I take note of which tps features are available 0.540
And I shutdown Tails and wait for the computer to power off 4.317
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.673
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.829
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 25.468
And I log in to a new session 20.552
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.573
And I plug USB drive "to_upgrade" 2.495
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.909
Then the running Tails is installed on USB drive "to_upgrade" 19.412
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 3.681
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.178
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.188
Then all tps features from the old Tails version are active 1.811
And Tails is running from USB drive "to_upgrade" 0.413
And the boot device has safe access rights 4.069
And the expected persistent files created with the old Tails version are present in the filesystem 1.777
And all persistent directories from the old Tails version have safe access rights 2.726
After features/support/hooks.rb:326 0.882
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:53.642
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.751
And no SquashFS delta is installed 0.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.067
And Tor is ready 18.403
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.589
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.339
Given I shutdown Tails and wait for the computer to power off 10.994
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.517
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.735
And the file system changes introduced in version 6.2~testoverlayfs are present 0.392
And only the 6.2~testoverlayfs SquashFS delta is installed 0.117
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.460
# 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.373
When the network is plugged 0.083
And Tor is ready 19.915
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.792
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.850
Given I shutdown Tails and wait for the computer to power off 6.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.064
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 5.355
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.577
And Tor is ready 43.463
Then the Upgrader considers the system as up-to-date 0.305
# 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.354
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.163
After features/support/hooks.rb:326 0.723
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
40.094
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 11.722
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 3.582
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.747
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 17.165
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.691
After features/support/hooks.rb:326 1.305
After features/support/hooks.rb:100 0.000