Project Number Date
test_Tails_ISO_devel 3796 29 Apr 2025, 22:19

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:8.724 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:18.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 30.515
When I start Tails from USB drive "old" with network unplugged 1:42.541
Then the boot device has safe access rights 3.040
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:330 7.436
After features/support/hooks.rb:100 0.012
Tags: @product
2:14.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:30.228
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 31.959
And I take note of which tps features are available 1.973
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 8.522
After features/support/hooks.rb:330 0.173
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.401
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.328
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.805
Then Tails is running from USB drive "old" 0.334
And all tps features are active 2.040
When I write some files expected to persist 2.630
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.510
And I take note of which tps features are available 0.437
And I shutdown Tails and wait for the computer to power off 6.615
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.078
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.794
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.203
And I log in to a new session 19.197
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.982
And I plug USB drive "to_upgrade" 2.526
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.475
Then the running Tails is installed on USB drive "to_upgrade" 22.001
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:330 0.880
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.071
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.389
Then all tps features from the old Tails version are active 1.708
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.530
And the expected persistent files created with the old Tails version are present in the filesystem 1.448
And all persistent directories from the old Tails version have safe access rights 2.464
After features/support/hooks.rb:330 1.208
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:3.451
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 11.201
And no SquashFS delta is installed 0.223
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
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.393
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.066
And Tor is ready 19.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.752
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.583
Given I shutdown Tails and wait for the computer to power off 8.840
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.444
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.281
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.428
# 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.368
When the network is plugged 0.070
And Tor is ready 19.096
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.763
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.001
Given I shutdown Tails and wait for the computer to power off 6.715
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.795
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.104
And the file system changes introduced in version 6.3~testoverlayfs are present 0.578
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.428
When the network is plugged 0.067
And Tor is ready 45.352
Then the Upgrader considers the system as up-to-date 0.328
# 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.643
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.428
After features/support/hooks.rb:330 0.760
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.499
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 10.460
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.512
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.125
But a current signing key is available on our website 0.000
When the network is plugged 0.102
And Tor is ready 18.897
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.350
After features/support/hooks.rb:330 1.551
After features/support/hooks.rb:100 0.000