Project Number Date
test_Tails_ISO_devel 3448 06 Jul 2024, 12:14

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 18:5.315 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:11.408
Before features/support/hooks.rb:269 0.020
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.436
When I start Tails from USB drive "old" with network unplugged 1:36.860
Then the boot device has safe access rights 2.837
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 6.889
After features/support/hooks.rb:100 0.007
Tags: @product
1:56.795
Before features/support/hooks.rb:269 0.004
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:17.005
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 30.726
And I take note of which tps features are available 1.367
Then a Tails persistence partition exists on USB drive "old" 0.872
And I shutdown Tails and wait for the computer to power off 6.331
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.511
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.989
Then Tails is running from USB drive "old" 0.285
And all tps features are active 1.918
When I write some files expected to persist 1.527
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.120
And I take note of which tps features are available 0.404
And I shutdown Tails and wait for the computer to power off 4.235
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.141
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.321
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 10.874
And I log in to a new session 18.605
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.435
And I plug USB drive "to_upgrade" 2.392
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.618
Then the running Tails is installed on USB drive "to_upgrade" 14.991
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:326 6.738
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.933
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.770
Then all tps features from the old Tails version are active 1.608
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.205
And the expected persistent files created with the old Tails version are present in the filesystem 1.440
And all persistent directories from the old Tails version have safe access rights 2.366
After features/support/hooks.rb:326 0.614
After features/support/hooks.rb:100 0.044
Tags: @product @automatic_upgrade
6:5.952
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 21.451
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.384
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.040
And Tor is ready 22.469
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.486
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.963
Given I shutdown Tails and wait for the computer to power off 8.384
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.608
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.971
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.351
# 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.297
When the network is plugged 0.041
And Tor is ready 17.938
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.227
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.349
Given I shutdown Tails and wait for the computer to power off 4.659
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.884
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.887
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.247
When the network is plugged 0.049
And Tor is ready 18.092
Then the Upgrader considers the system as up-to-date 0.304
# 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 12.831
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.700
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
33.393
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.806
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.410
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.887
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 17.079
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.077
After features/support/hooks.rb:326 0.661
After features/support/hooks.rb:100 0.000