Project Number Date
test_Tails_ISO_devel 3729 07 Mar 2025, 13: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 21:9.446 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:41.389
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.262
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 1:0.831
When I start Tails from USB drive "old" with network unplugged 1:34.924
Then the boot device has safe access rights 3.179
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.365
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:330 3.559
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.279
And I start Tails from USB drive "old" with network unplugged and I login 1:23.780
Then Tails is running from USB drive "old" 0.421
And I create a persistent partition 33.275
And I take note of which tps features are available 2.349
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 8.508
After features/support/hooks.rb:330 0.175
After features/support/hooks.rb:100 0.012
Tags: @product
2:55.228
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.592
Then Tails is running from USB drive "old" 0.598
And all tps features are active 2.118
When I write some files expected to persist 1.906
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.487
And all persistent directories from the old Tails version have safe access rights 2.681
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 6.946
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.920
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.649
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 without a persistent partition and stopped at Tails Greeter's login screen 11.206
And I log in to a new session 20.841
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.848
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.230
Then the running Tails is installed on USB drive "to_upgrade" 24.325
And I unplug USB drive "to_upgrade" 0.366
And I unplug USB drive "__internal" 0.358
After features/support/hooks.rb:330 2.534
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.203
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.281
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.011
Then all tps features from the old Tails version are active 1.730
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.685
And the expected persistent files created with the old Tails version are present in the filesystem 1.511
And all persistent directories from the old Tails version have safe access rights 2.640
After features/support/hooks.rb:330 0.903
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:32.103
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 30.158
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.598
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.490
When the network is plugged 0.087
And Tor is ready 25.252
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.452
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.079
Given I shutdown Tails and wait for the computer to power off 11.729
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.956
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.299
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.290
# 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.276
When the network is plugged 0.230
And Tor is ready 20.089
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.220
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.962
Given I shutdown Tails and wait for the computer to power off 8.543
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.015
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.207
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.066
And Tor is ready 22.451
Then the Upgrader considers the system as up-to-date 0.351
# 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 15.721
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.403
After features/support/hooks.rb:330 0.866
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
41.369
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.547
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.522
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 22.731
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.371
After features/support/hooks.rb:330 0.930
After features/support/hooks.rb:100 0.000