Project Number Date
test_Tails_ISO_feature-arti 103 01 Jul 2025, 17:47

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:59.630 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:14.185
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 29.730
When I start Tails from USB drive "old" with network unplugged 1:38.369
Then the boot device has safe access rights 3.586
And Tails is running from USB drive "old" 0.500
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:330 7.191
After features/support/hooks.rb:100 0.010
Tags: @product
2:19.899
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login 1:33.866
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 33.064
And I take note of which tps features are available 2.467
Then a Tails persistence partition exists on USB drive "old" 0.962
And I shutdown Tails and wait for the computer to power off 8.951
After features/support/hooks.rb:330 0.167
After features/support/hooks.rb:100 0.009
Tags: @product
3:8.468
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.284
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.827
Then Tails is running from USB drive "old" 0.451
And all tps features are active 2.094
When I write some files expected to persist 2.045
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.396
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.286
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 4.441
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.759
After features/support/hooks.rb:330 0.118
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.512
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.079
And I log in to a new session 21.824
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.445
And I plug USB drive "to_upgrade" 2.604
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.366
Then the running Tails is installed on USB drive "to_upgrade" 30.600
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.400
After features/support/hooks.rb:330 0.997
After features/support/hooks.rb:100 0.000
Tags: @product
2:34.033
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.269
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.417
Then all tps features from the old Tails version are active 1.702
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.651
And the expected persistent files created with the old Tails version are present in the filesystem 1.534
And all persistent directories from the old Tails version have safe access rights 3.099
After features/support/hooks.rb:330 1.757
After features/support/hooks.rb:100 0.009
7:21.505
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.043
And no SquashFS delta is installed 0.136
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.137
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.616
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.500
When the network is plugged 0.068
And Tor is ready 50.156
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.637
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.124
Given I shutdown Tails and wait for the computer to power off 10.012
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.837
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.430
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.271
When the network is plugged 0.071
And Tor is ready 19.458
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.944
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.219
Given I shutdown Tails and wait for the computer to power off 6.535
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.420
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.345
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.076
And Tor is ready 19.941
Then the Upgrader considers the system as up-to-date 0.424
# 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 16.982
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.865
After features/support/hooks.rb:330 0.887
After features/support/hooks.rb:100 0.034
39.025
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.581
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 20.031
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.821
After features/support/hooks.rb:330 0.877
After features/support/hooks.rb:100 0.000