Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 56 28 Jul 2026, 08:05

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:25.638 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:8.086
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.226
When I start Tails from USB drive "old" with network unplugged 50.251
Then the boot device has safe access rights 2.774
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:339 3.534
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.006
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 52.633
Then Tails is running from USB drive "old" 0.222
And I create a persistent partition 24.521
And I take note of which tps features are available 4.011
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 3.980
After features/support/hooks.rb:339 0.392
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.647
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.165
Then Tails is running from USB drive "old" 0.236
And all tps features are active 4.480
When I write some files expected to persist 1.196
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.268
And all persistent directories from the old Tails version have safe access rights 1.971
And I take note of which tps features are available 4.024
And I shutdown Tails and wait for the computer to power off 4.271
# 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" 11.814
After features/support/hooks.rb:339 0.182
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.107
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 without a persistent partition and stopped at Tails Greeter's login screen 7.394
And I log in to a new session 11.872
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.731
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.108
Then the running Tails is installed on USB drive "to_upgrade" 14.522
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 0.804
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.026
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.337
Then all tps features from the old Tails version are active 0.954
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 2.364
And the expected persistent files created with the old Tails version are present in the filesystem 1.062
And all persistent directories from the old Tails version have safe access rights 2.032
After features/support/hooks.rb:339 0.659
After features/support/hooks.rb:108 0.031
3:42.944
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.886
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.184
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.331
When the network is plugged 0.022
And Tor is ready 11.945
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.121
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.558
Given I shutdown Tails and wait for the computer to power off 5.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.500
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.008
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.209
When the network is plugged 0.016
And Tor is ready 11.738
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.243
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.953
Given I shutdown Tails and wait for the computer to power off 4.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.647
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.381
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.015
And Tor is ready 10.981
Then the Upgrader considers the system as up-to-date 10.690
# 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.101
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.371
After features/support/hooks.rb:339 0.959
After features/support/hooks.rb:108 0.010
20.820
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.456
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.057
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.873
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.173
After features/support/hooks.rb:339 0.898
After features/support/hooks.rb:108 0.000