Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 7 11 Mar 2025, 07:15

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:30.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:12.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
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" 33.363
When I start Tails from USB drive "old" with network unplugged 1:34.196
Then the boot device has safe access rights 2.993
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:330 3.511
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.575
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:33.270
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 31.034
And I take note of which tps features are available 2.057
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 8.879
After features/support/hooks.rb:330 0.193
After features/support/hooks.rb:100 0.011
Tags: @product
3:16.740
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:36.128
Then Tails is running from USB drive "old" 0.544
And all tps features are active 2.449
When I write some files expected to persist 2.339
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.449
And all persistent directories from the old Tails version have safe access rights 2.768
And I take note of which tps features are available 0.559
And I shutdown Tails and wait for the computer to power off 6.792
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.243
After features/support/hooks.rb:330 0.124
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.919
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 11.323
And I log in to a new session 18.214
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.540
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.395
Then the running Tails is installed on USB drive "to_upgrade" 18.516
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:330 2.224
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.310
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.619
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.387
Then all tps features from the old Tails version are active 1.725
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 3.400
And the expected persistent files created with the old Tails version are present in the filesystem 1.445
And all persistent directories from the old Tails version have safe access rights 3.423
After features/support/hooks.rb:330 1.383
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:10.478
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.472
And no SquashFS delta is installed 0.145
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.504
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.480
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.483
When the network is plugged 0.068
And Tor is ready 22.574
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.776
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.240
Given I shutdown Tails and wait for the computer to power off 13.031
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.161
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.178
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
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.299
# 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.267
When the network is plugged 0.087
And Tor is ready 20.695
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.299
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.801
Given I shutdown Tails and wait for the computer to power off 4.355
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.187
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.090
And the file system changes introduced in version 6.3~testoverlayfs are present 0.640
And only the 6.3~testoverlayfs SquashFS delta is installed 0.151
# 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.370
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.089
And Tor is ready 47.843
Then the Upgrader considers the system as up-to-date 0.309
# 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 15.003
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.038
After features/support/hooks.rb:330 0.722
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
37.171
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.737
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.665
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the signing key used by the Upgrader is outdated 0.113
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 18.763
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.683
After features/support/hooks.rb:330 1.548
After features/support/hooks.rb:100 0.000