Project Number Date
test_Tails_ISO_stable 5662 19 May 2025, 23:09

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:0.512 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:35.047
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 37.624
When I start Tails from USB drive "old" with network unplugged 1:52.123
Then the boot device has safe access rights 2.934
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 3.787
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.054
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:29.859
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 32.492
And I take note of which tps features are available 2.492
Then a Tails persistence partition exists on USB drive "old" 1.210
And I shutdown Tails and wait for the computer to power off 8.434
After features/support/hooks.rb:330 0.223
After features/support/hooks.rb:100 0.015
Tags: @product
2:55.125
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.777
Then Tails is running from USB drive "old" 0.399
And all tps features are active 2.028
When I write some files expected to persist 1.770
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.333
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.476
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.105
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.018
Tags: @product
2:38.732
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 12.283
And I log in to a new session 20.859
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.649
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.212
Then the running Tails is installed on USB drive "to_upgrade" 26.903
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 3.772
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.629
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.386
Then all tps features from the old Tails version are active 1.643
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 4.106
And the expected persistent files created with the old Tails version are present in the filesystem 1.498
And all persistent directories from the old Tails version have safe access rights 2.435
After features/support/hooks.rb:330 1.060
After features/support/hooks.rb:100 0.086
Tags: @product @automatic_upgrade
6:40.219
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.646
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.524
When the network is plugged 0.062
And Tor is ready 17.865
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.044
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.181
Given I shutdown Tails and wait for the computer to power off 11.535
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.326
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.084
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.294
When the network is plugged 0.073
And Tor is ready 18.789
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.054
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.999
Given I shutdown Tails and wait for the computer to power off 4.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.223
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.099
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.073
And Tor is ready 17.996
Then the Upgrader considers the system as up-to-date 0.342
# 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.231
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.696
After features/support/hooks.rb:330 0.770
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.703
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 10.196
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.126
And the signing key used by the Upgrader is outdated 0.124
But a current signing key is available on our website 0.000
When the network is plugged 0.122
And Tor is ready 19.381
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.410
After features/support/hooks.rb:330 0.808
After features/support/hooks.rb:100 0.000