Project Number Date
test_Tails_ISO_devel 3695 17 Feb 2025, 09:43

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 19:17.538 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:5.287
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.879
When I start Tails from USB drive "old" with network unplugged 1:28.272
Then the boot device has safe access rights 2.825
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 3.745
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.318
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:27.721
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 32.632
And I take note of which tps features are available 1.451
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.219
After features/support/hooks.rb:326 0.252
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.358
Before features/support/hooks.rb:269 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.465
Then Tails is running from USB drive "old" 0.336
And all tps features are active 2.001
When I write some files expected to persist 1.785
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.503
And all persistent directories from the old Tails version have safe access rights 2.536
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 4.338
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.498
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.756
Before features/support/hooks.rb:269 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.541
And I log in to a new session 19.932
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.325
And I plug USB drive "to_upgrade" 2.461
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.420
Then the running Tails is installed on USB drive "to_upgrade" 22.672
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 6.602
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.931
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.283
Then all tps features from the old Tails version are active 1.734
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.246
And the expected persistent files created with the old Tails version are present in the filesystem 1.491
And all persistent directories from the old Tails version have safe access rights 2.626
After features/support/hooks.rb:326 0.779
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:38.935
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.768
And no SquashFS delta is installed 1.016
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.401
When the network is plugged 0.080
And Tor is ready 50.933
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.918
Given I shutdown Tails and wait for the computer to power off 8.448
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.254
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.250
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
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.304
# 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.240
When the network is plugged 0.080
And Tor is ready 19.808
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.081
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.892
Given I shutdown Tails and wait for the computer to power off 4.167
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.220
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.896
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.072
And Tor is ready 21.800
Then the Upgrader considers the system as up-to-date 0.291
# 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.299
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.972
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.950
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.504
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.176
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 21.684
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.390
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.000