Project Number Date
test_Tails_ISO_devel 3494 27 Aug 2024, 12:42

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:20.261 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:5.659
Before features/support/hooks.rb:269 0.006
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 29.645
When I start Tails from USB drive "old" with network unplugged 1:30.652
Then the boot device has safe access rights 2.981
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.233
After features/support/hooks.rb:326 6.859
After features/support/hooks.rb:100 0.011
Tags: @product
2:5.920
Before features/support/hooks.rb:269 0.005
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:23.164
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 31.544
And I take note of which tps features are available 1.485
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.367
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.011
Tags: @product
2:51.997
Before features/support/hooks.rb:269 0.007
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.282
Then Tails is running from USB drive "old" 0.317
And all tps features are active 1.882
When I write some files expected to persist 1.716
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.477
And all persistent directories from the old Tails version have safe access rights 2.647
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 4.307
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.475
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.011
Tags: @product
2:28.267
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.179
And I log in to a new session 18.633
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.416
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.990
Then the running Tails is installed on USB drive "to_upgrade" 17.195
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.748
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.202
Before features/support/hooks.rb:269 0.007
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.398
Then all tps features from the old Tails version are active 1.672
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.715
And the expected persistent files created with the old Tails version are present in the filesystem 1.476
And all persistent directories from the old Tails version have safe access rights 2.429
After features/support/hooks.rb:326 0.784
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:39.489
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 11.978
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.150
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.078
And Tor is ready 17.767
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.787
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.563
Given I shutdown Tails and wait for the computer to power off 8.485
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.198
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.291
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.264
When the network is plugged 0.063
And Tor is ready 18.450
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.096
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.030
Given I shutdown Tails and wait for the computer to power off 4.254
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.206
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 2.368
And the file system changes introduced in version 6.3~testoverlayfs are present 0.573
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.382
When the network is plugged 0.231
And Tor is ready 18.133
Then the Upgrader considers the system as up-to-date 0.345
# 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.342
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.116
After features/support/hooks.rb:326 0.855
After features/support/hooks.rb:100 0.083
Tags: @product @automatic_upgrade
58.723
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.334
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.851
But a current signing key is available on our website 0.000
When the network is plugged 0.130
And Tor is ready 45.421
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.620
After features/support/hooks.rb:326 1.997
After features/support/hooks.rb:100 0.000