Project Number Date
test_Tails_ISO_20267-webtunnel 1 09 Jul 2025, 03:39

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 25:35.090 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:25.748
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 37.096
When I start Tails from USB drive "old" with network unplugged 1:42.869
Then the boot device has safe access rights 3.362
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.375
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:330 5.815
After features/support/hooks.rb:100 0.042
Tags: @product
2:41.163
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.051
Given a computer 0.621
And I start Tails from USB drive "old" with network unplugged and I login 1:46.334
Then Tails is running from USB drive "old" 0.653
And I create a persistent partition 37.107
And I take note of which tps features are available 3.383
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 12.232
After features/support/hooks.rb:330 0.104
After features/support/hooks.rb:100 0.026
Tags: @product
3:48.709
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.580
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:54.770
Then Tails is running from USB drive "old" 3.656
And all tps features are active 2.902
When I write some files expected to persist 2.329
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.548
And all persistence configuration files have safe access rights 0.519
And all persistent directories from the old Tails version have safe access rights 2.723
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 4.681
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.538
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.013
Tags: @product
3:17.328
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.647
And I log in to a new session 25.897
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.616
And I plug USB drive "to_upgrade" 2.408
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:54.757
Then the running Tails is installed on USB drive "to_upgrade" 37.279
And I unplug USB drive "to_upgrade" 0.438
And I unplug USB drive "__internal" 0.281
After features/support/hooks.rb:330 2.216
After features/support/hooks.rb:100 0.000
Tags: @product
3:19.930
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:3.294
Then all tps features from the old Tails version are active 1.722
And Tails is running from USB drive "to_upgrade" 0.533
And the boot device has safe access rights 9.422
And the expected persistent files created with the old Tails version are present in the filesystem 2.165
And all persistent directories from the old Tails version have safe access rights 2.583
After features/support/hooks.rb:330 1.475
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
9:18.359
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 33.010
And no SquashFS delta is installed 0.313
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.740
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.150
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.421
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.759
When the network is plugged 0.140
And Tor is ready 22.471
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.168
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.271
Given I shutdown Tails and wait for the computer to power off 13.487
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:46.113
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 5.861
And the file system changes introduced in version 6.2~testoverlayfs are present 0.832
And only the 6.2~testoverlayfs SquashFS delta is installed 0.167
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.520
# 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.600
When the network is plugged 0.090
And Tor is ready 21.370
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.736
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.251
Given I shutdown Tails and wait for the computer to power off 7.816
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:50.733
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 3.369
And the file system changes introduced in version 6.3~testoverlayfs are present 0.745
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.435
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.462
When the network is plugged 0.095
And Tor is ready 30.222
Then the Upgrader considers the system as up-to-date 0.356
# 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 22.667
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.871
After features/support/hooks.rb:330 0.698
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
43.850
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 13.539
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 21.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.615
After features/support/hooks.rb:330 0.950
After features/support/hooks.rb:100 0.000