Project Number Date
test_Tails_ISO_20904-tor-browser-14.5-force-all-tests 3 23 Apr 2025, 14:59

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:48.253 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:23.872
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 39.550
When I start Tails from USB drive "old" with network unplugged 1:38.525
Then the boot device has safe access rights 3.344
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:330 13.207
After features/support/hooks.rb:100 0.013
Tags: @product
2:18.414
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:32.778
Then Tails is running from USB drive "old" 0.426
And I create a persistent partition 32.776
And I take note of which tps features are available 2.555
Then a Tails persistence partition exists on USB drive "old" 0.937
And I shutdown Tails and wait for the computer to power off 8.727
After features/support/hooks.rb:330 0.221
After features/support/hooks.rb:100 0.021
Tags: @product
3:13.322
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:34.343
Then Tails is running from USB drive "old" 0.560
And all tps features are active 2.265
When I write some files expected to persist 1.947
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.273
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.844
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 4.599
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.279
After features/support/hooks.rb:330 0.166
After features/support/hooks.rb:100 0.020
Tags: @product
2:43.661
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.896
And I log in to a new session 20.370
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.568
And I plug USB drive "to_upgrade" 2.493
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.848
Then the running Tails is installed on USB drive "to_upgrade" 29.032
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:330 0.786
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.004
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.924
Then all tps features from the old Tails version are active 1.728
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 4.018
And the expected persistent files created with the old Tails version are present in the filesystem 1.851
And all persistent directories from the old Tails version have safe access rights 2.899
After features/support/hooks.rb:330 1.986
After features/support/hooks.rb:100 0.010
7:4.611
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 12.755
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.568
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.452
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.859
When the network is plugged 0.070
And Tor is ready 20.058
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.708
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.166
Given I shutdown Tails and wait for the computer to power off 11.215
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.360
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.485
And the file system changes introduced in version 6.2~testoverlayfs are present 0.356
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.281
When the network is plugged 0.081
And Tor is ready 19.053
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.474
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.810
Given I shutdown Tails and wait for the computer to power off 4.777
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.882
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 3.117
And the file system changes introduced in version 6.3~testoverlayfs are present 0.576
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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.060
And Tor is ready 18.627
Then the Upgrader considers the system as up-to-date 0.432
# 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.415
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.640
After features/support/hooks.rb:330 0.779
After features/support/hooks.rb:100 0.037
36.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.372
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.574
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
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.086
And Tor is ready 18.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.705
After features/support/hooks.rb:330 1.291
After features/support/hooks.rb:100 0.000