Project Number Date
test_Tails_ISO_stable 5361 30 Dec 2024, 12:17

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:44.289 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
1:59.694
Before features/support/hooks.rb:269 0.005
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.974
When I start Tails from USB drive "old" with network unplugged 1:23.415
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 7.522
After features/support/hooks.rb:100 0.010
Tags: @product
2:4.849
Before features/support/hooks.rb:269 0.013
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 1:22.349
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 31.559
And I take note of which tps features are available 1.474
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.143
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.447
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.815
Then Tails is running from USB drive "old" 0.312
And all tps features are active 1.893
When I write some files expected to persist 1.803
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.319
And all persistence configuration files have safe access rights 0.535
And all persistent directories from the old Tails version have safe access rights 2.465
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 4.382
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.274
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.946
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.021
And I log in to a new session 19.296
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.586
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.866
Then the running Tails is installed on USB drive "to_upgrade" 19.350
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 1.982
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.293
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.041
Then all tps features from the old Tails version are active 1.681
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.163
And the expected persistent files created with the old Tails version are present in the filesystem 1.570
And all persistent directories from the old Tails version have safe access rights 2.346
After features/support/hooks.rb:326 0.616
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:19.585
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 12.305
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.076
And Tor is ready 21.657
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.125
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.524
Given I shutdown Tails and wait for the computer to power off 10.655
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.802
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.193
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.288
When the network is plugged 0.078
And Tor is ready 17.302
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.240
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.652
Given I shutdown Tails and wait for the computer to power off 4.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.067
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.245
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.368
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.075
And Tor is ready 18.802
Then the Upgrader considers the system as up-to-date 0.317
# 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.803
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.975
After features/support/hooks.rb:326 0.689
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.472
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 10.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.613
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 19.202
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.326
After features/support/hooks.rb:326 0.869
After features/support/hooks.rb:100 0.000