Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 29 01 Apr 2025, 06:19

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:27.211 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:7.331
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.408
When I start Tails from USB drive "old" with network unplugged 1:31.545
Then the boot device has safe access rights 3.045
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 7.188
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.061
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:23.044
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 31.776
And I take note of which tps features are available 1.534
Then a Tails persistence partition exists on USB drive "old" 0.814
And I shutdown Tails and wait for the computer to power off 8.327
After features/support/hooks.rb:330 0.183
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.197
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.285
Then Tails is running from USB drive "old" 0.598
And all tps features are active 1.871
When I write some files expected to persist 1.923
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.559
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.524
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.072
After features/support/hooks.rb:330 0.127
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.449
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 9.876
And I log in to a new session 18.654
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.659
And I plug USB drive "to_upgrade" 2.345
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.050
Then the running Tails is installed on USB drive "to_upgrade" 22.460
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:330 2.075
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.130
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.782
Then all tps features from the old Tails version are active 1.627
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 3.407
And the expected persistent files created with the old Tails version are present in the filesystem 1.373
And all persistent directories from the old Tails version have safe access rights 2.434
After features/support/hooks.rb:330 1.336
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:47.353
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.910
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.086
And Tor is ready 24.853
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.480
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.003
Given I shutdown Tails and wait for the computer to power off 8.435
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.492
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.003
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.286
# 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.247
When the network is plugged 0.064
And Tor is ready 18.840
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.457
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.457
Given I shutdown Tails and wait for the computer to power off 4.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.960
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.144
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.270
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.089
And Tor is ready 20.137
Then the Upgrader considers the system as up-to-date 0.325
# 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.502
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.573
After features/support/hooks.rb:330 0.729
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.687
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.455
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.101
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 18.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.938
After features/support/hooks.rb:330 0.647
After features/support/hooks.rb:100 0.000