Project Number Date
test_Tails_ISO_stable 5531 26 Mar 2025, 13:36

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 22:7.607 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:56.131
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.345
And I create a 7200 MiB disk named "old" 0.517
And I plug USB drive "old" 1.127
And I write an old version of the Tails USB image to disk "old" 1:1.373
When I start Tails from USB drive "old" with network unplugged 1:48.383
Then the boot device has safe access rights 3.374
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:330 11.891
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.294
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:35.950
Then Tails is running from USB drive "old" 0.378
And I create a persistent partition 32.411
And I take note of which tps features are available 2.169
Then a Tails persistence partition exists on USB drive "old" 0.850
And I shutdown Tails and wait for the computer to power off 8.303
After features/support/hooks.rb:330 0.197
After features/support/hooks.rb:100 0.009
Tags: @product
3:6.466
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.267
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.961
Then Tails is running from USB drive "old" 0.470
And all tps features are active 2.645
When I write some files expected to persist 2.131
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.513
And all persistent directories from the old Tails version have safe access rights 2.571
And I take note of which tps features are available 0.620
And I shutdown Tails and wait for the computer to power off 4.352
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.683
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.192
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 16.065
And I log in to a new session 22.595
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.013
And I plug USB drive "to_upgrade" 2.491
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.796
Then the running Tails is installed on USB drive "to_upgrade" 25.719
And I unplug USB drive "to_upgrade" 0.258
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:330 2.556
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.692
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.272
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.420
Then all tps features from the old Tails version are active 2.337
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.697
And the expected persistent files created with the old Tails version are present in the filesystem 1.735
And all persistent directories from the old Tails version have safe access rights 2.873
After features/support/hooks.rb:330 1.706
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:34.859
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 18.480
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.460
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.349
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.520
When the network is plugged 0.292
And Tor is ready 23.023
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.364
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.821
Given I shutdown Tails and wait for the computer to power off 13.811
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:30.037
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 5.257
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.318
When the network is plugged 0.358
And Tor is ready 16.025
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.173
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.429
Given I shutdown Tails and wait for the computer to power off 6.505
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.576
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 3.793
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.081
And Tor is ready 18.827
Then the Upgrader considers the system as up-to-date 0.784
# 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.401
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.990
After features/support/hooks.rb:330 1.160
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
42.971
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 14.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.136
But a current signing key is available on our website 0.000
When the network is plugged 0.885
And Tor is ready 20.087
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.273
After features/support/hooks.rb:330 1.204
After features/support/hooks.rb:100 0.000