Project Number Date
test_Tails_ISO_stable 4700 05 Mar 2024, 17:20

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 18:6.167 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
1:27.768
Before features/support/hooks.rb:245 0.008
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 18.590
When I start Tails from USB drive "old" with network unplugged 1:4.079
Then the boot device has safe access rights 2.913
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:291 6.676
After features/support/hooks.rb:75 0.010
Tags: @product
2:7.025
Before features/support/hooks.rb:245 0.006
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login 1:14.507
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 41.543
And I take note of which tps features are available 1.714
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 8.024
After features/support/hooks.rb:291 0.161
After features/support/hooks.rb:75 0.010
Tags: @product
2:39.129
Before features/support/hooks.rb:245 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.189
Then Tails is running from USB drive "old" 0.325
And all tps features are active 1.773
When I write some files expected to persist 1.680
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.366
And I take note of which tps features are available 0.291
And I shutdown Tails and wait for the computer to power off 4.106
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.555
After features/support/hooks.rb:291 0.132
After features/support/hooks.rb:75 0.011
Tags: @product
2:29.820
Before features/support/hooks.rb:245 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 10.002
And I log in to a new session 16.676
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.371
And I plug USB drive "to_upgrade" 2.465
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.627
Then the running Tails is installed on USB drive "to_upgrade" 13.257
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:291 3.535
After features/support/hooks.rb:75 0.000
Tags: @product
2:18.745
Before features/support/hooks.rb:245 0.008
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.271
Then all tps features from the old Tails version are active 1.296
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 2.910
And the expected persistent files created with the old Tails version are present in the filesystem 1.455
And all persistent directories from the old Tails version have safe access rights 2.317
After features/support/hooks.rb:291 0.779
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
6:27.976
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.808
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.029
And Tor is ready 20.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.288
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.302
Given I shutdown Tails and wait for the computer to power off 6.025
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.884
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.737
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.251
When the network is plugged 0.025
And Tor is ready 16.419
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.432
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.022
Given I shutdown Tails and wait for the computer to power off 4.035
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.715
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 1.520
And the file system changes introduced in version 6.3~testoverlayfs are present 0.449
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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.028
And Tor is ready 14.315
Then the Upgrader considers the system as up-to-date 0.248
# 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 12.591
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.875
After features/support/hooks.rb:291 0.793
After features/support/hooks.rb:75 0.016
Tags: @product @automatic_upgrade
35.701
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.311
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.513
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 19.241
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.233
After features/support/hooks.rb:291 0.679
After features/support/hooks.rb:75 0.000