Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 36 09 Jul 2026, 08:11

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:39.335 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.011
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.696
When I start Tails from USB drive "old" with network unplugged 49.811
Then the boot device has safe access rights 2.669
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.252
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 1.562
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.092
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 52.539
Then Tails is running from USB drive "old" 0.256
And I create a persistent partition 24.788
And I take note of which tps features are available 4.006
Then a Tails persistence partition exists on USB drive "old" 0.566
And I shutdown Tails and wait for the computer to power off 7.864
After features/support/hooks.rb:339 0.315
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.383
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.608
Then Tails is running from USB drive "old" 0.246
And all tps features are active 4.952
When I write some files expected to persist 1.403
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.305
And all persistent directories from the old Tails version have safe access rights 2.044
And I take note of which tps features are available 3.700
And I shutdown Tails and wait for the computer to power off 2.676
# 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.200
After features/support/hooks.rb:339 0.493
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.430
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.322
And I log in to a new session 11.727
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.797
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.168
Then the running Tails is installed on USB drive "to_upgrade" 14.939
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 2.145
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.893
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.911
Then all tps features from the old Tails version are active 1.156
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 2.493
And the expected persistent files created with the old Tails version are present in the filesystem 1.037
And all persistent directories from the old Tails version have safe access rights 1.913
After features/support/hooks.rb:339 0.904
After features/support/hooks.rb:108 0.005
3:50.363
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 8.094
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.181
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.021
And Tor is ready 13.502
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.397
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.633
Given I shutdown Tails and wait for the computer to power off 9.621
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.786
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.503
And the file system changes introduced in version 6.2~testoverlayfs are present 0.195
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.175
# 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.188
When the network is plugged 0.017
And Tor is ready 11.307
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.139
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.735
Given I shutdown Tails and wait for the computer to power off 7.959
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.038
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.815
And the file system changes introduced in version 6.3~testoverlayfs are present 0.345
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.015
And Tor is ready 10.512
Then the Upgrader considers the system as up-to-date 10.499
# 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.207
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.369
After features/support/hooks.rb:339 1.056
After features/support/hooks.rb:108 0.010
21.161
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.655
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.888
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.285
After features/support/hooks.rb:339 0.633
After features/support/hooks.rb:108 0.000