Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 53 25 Jul 2026, 08:12

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 11:41.660 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:15.738
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.380
When I start Tails from USB drive "old" with network unplugged 57.916
Then the boot device has safe access rights 2.730
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 1.367
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.544
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 53.458
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 24.039
And I take note of which tps features are available 4.012
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 4.096
After features/support/hooks.rb:339 0.342
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.406
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.789
Then Tails is running from USB drive "old" 0.244
And all tps features are active 4.720
When I write some files expected to persist 1.427
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 1.907
And I take note of which tps features are available 3.733
And I shutdown Tails and wait for the computer to power off 3.955
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.020
After features/support/hooks.rb:339 0.436
After features/support/hooks.rb:108 0.007
Tags: @product
2:10.758
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.158
And I log in to a new session 13.160
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.725
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.603
Then the running Tails is installed on USB drive "to_upgrade" 14.599
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 2.131
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.672
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.024
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.100
Then all tps features from the old Tails version are active 0.937
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.432
And the expected persistent files created with the old Tails version are present in the filesystem 0.975
And all persistent directories from the old Tails version have safe access rights 1.905
After features/support/hooks.rb:339 0.538
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:46.802
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.831
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.014
And Tor is ready 12.035
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.320
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.627
Given I shutdown Tails and wait for the computer to power off 5.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.181
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 4.349
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.097
# 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.186
When the network is plugged 0.016
And Tor is ready 11.109
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.459
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.629
Given I shutdown Tails and wait for the computer to power off 4.041
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.349
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.817
And the file system changes introduced in version 6.3~testoverlayfs are present 0.377
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.181
When the network is plugged 0.041
And Tor is ready 11.176
Then the Upgrader considers the system as up-to-date 10.512
# 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 4.196
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.339
After features/support/hooks.rb:339 0.610
After features/support/hooks.rb:108 0.062
Tags: @product @automatic_upgrade
20.737
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.223
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.172
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.032
After features/support/hooks.rb:339 1.029
After features/support/hooks.rb:108 0.000