Project Number Date
test_Tails_ISO_feature-arti 106 04 Jul 2025, 17:26

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:10.935 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.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.327
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 32.349
When I start Tails from USB drive "old" with network unplugged 1:46.264
Then the boot device has safe access rights 3.715
And Tails is running from USB drive "old" 0.604
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:330 3.968
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.639
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:30.630
Then Tails is running from USB drive "old" 0.396
And I create a persistent partition 31.791
And I take note of which tps features are available 2.103
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.685
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.038
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.932
Then Tails is running from USB drive "old" 0.380
And all tps features are active 1.858
When I write some files expected to persist 1.915
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.415
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 4.264
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.024
After features/support/hooks.rb:330 0.087
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.300
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.678
And I log in to a new session 20.262
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.697
And I plug USB drive "to_upgrade" 2.437
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.579
Then the running Tails is installed on USB drive "to_upgrade" 27.222
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:330 2.216
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.437
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.591
Then all tps features from the old Tails version are active 1.964
And Tails is running from USB drive "to_upgrade" 0.375
And the boot device has safe access rights 3.400
And the expected persistent files created with the old Tails version are present in the filesystem 1.468
And all persistent directories from the old Tails version have safe access rights 2.455
After features/support/hooks.rb:330 1.319
After features/support/hooks.rb:100 0.040
Tags: @product @automatic_upgrade
6:52.607
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.040
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.077
And Tor is ready 24.111
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.081
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.739
Given I shutdown Tails and wait for the computer to power off 8.952
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.320
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.343
And the file system changes introduced in version 6.2~testoverlayfs are present 0.368
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.236
When the network is plugged 0.073
And Tor is ready 19.498
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.360
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.053
Given I shutdown Tails and wait for the computer to power off 4.708
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.360
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.037
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.098
And Tor is ready 18.286
Then the Upgrader considers the system as up-to-date 10.843
# 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.227
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.816
After features/support/hooks.rb:330 0.675
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.816
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.803
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the signing key used by the Upgrader is outdated 0.142
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 20.145
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.267
After features/support/hooks.rb:330 2.497
After features/support/hooks.rb:100 0.000