Project Number Date
test_Tails_ISO_devel 3629 01 Jan 2025, 12:26

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:0.035 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:53.694
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.366
When I start Tails from USB drive "old" with network unplugged 1:20.108
Then the boot device has safe access rights 2.956
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.273
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 3.513
After features/support/hooks.rb:100 0.010
Tags: @product
2:4.626
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:20.407
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 32.593
And I take note of which tps features are available 1.582
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 8.624
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.012
Tags: @product
2:46.661
Before features/support/hooks.rb:269 0.010
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.585
Then Tails is running from USB drive "old" 0.292
And all tps features are active 1.958
When I write some files expected to persist 1.932
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.365
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.189
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.104
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.190
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.849
And I log in to a new session 20.818
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.508
And I plug USB drive "to_upgrade" 2.444
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.872
Then the running Tails is installed on USB drive "to_upgrade" 21.275
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 2.199
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.456
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.731
Then all tps features from the old Tails version are active 1.851
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.494
And the expected persistent files created with the old Tails version are present in the filesystem 1.429
And all persistent directories from the old Tails version have safe access rights 2.412
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:50.392
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 25.939
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.569
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.080
And Tor is ready 23.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.390
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.582
Given I shutdown Tails and wait for the computer to power off 8.601
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.283
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.239
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
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.260
# 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.266
When the network is plugged 0.089
And Tor is ready 19.430
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.690
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.875
Given I shutdown Tails and wait for the computer to power off 4.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.182
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.972
And the file system changes introduced in version 6.3~testoverlayfs are present 0.553
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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.072
And Tor is ready 16.860
Then the Upgrader considers the system as up-to-date 0.336
# 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.816
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.097
After features/support/hooks.rb:326 0.659
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.013
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.592
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.911
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 22.935
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.116
After features/support/hooks.rb:326 0.677
After features/support/hooks.rb:100 0.000