Project Number Date
test_Tails_ISO_stable 5071 04 Sep 2024, 20:42

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:2.800 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:3.829
Before features/support/hooks.rb:269 0.007
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 30.835
When I start Tails from USB drive "old" with network unplugged 1:27.616
Then the boot device has safe access rights 3.119
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.596
After features/support/hooks.rb:100 0.013
Tags: @product
2:4.184
Before features/support/hooks.rb:269 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:21.540
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 31.624
And I take note of which tps features are available 1.393
Then a Tails persistence partition exists on USB drive "old" 0.900
And I shutdown Tails and wait for the computer to power off 8.174
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.850
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.210
Then Tails is running from USB drive "old" 0.378
And all tps features are active 2.301
When I write some files expected to persist 1.649
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.342
And I take note of which tps features are available 0.378
And I shutdown Tails and wait for the computer to power off 4.346
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.484
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.014
Tags: @product
2:41.555
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.329
And I log in to a new session 25.520
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.571
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.553
Then the running Tails is installed on USB drive "to_upgrade" 20.762
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 2.025
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.610
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.661
Then all tps features from the old Tails version are active 1.794
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.342
And the expected persistent files created with the old Tails version are present in the filesystem 1.536
And all persistent directories from the old Tails version have safe access rights 2.788
After features/support/hooks.rb:326 1.165
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:8.698
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.221
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.433
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.353
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.589
When the network is plugged 0.079
And Tor is ready 19.575
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.272
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.386
Given I shutdown Tails and wait for the computer to power off 10.668
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.459
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.310
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.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.303
When the network is plugged 0.070
And Tor is ready 19.378
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.598
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.863
Given I shutdown Tails and wait for the computer to power off 4.353
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.644
Then Tails is running version 6.3~testoverlayfs 0.043
And all tps features are active 2.139
And the file system changes introduced in version 6.3~testoverlayfs are present 0.549
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.401
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.089
And Tor is ready 18.856
Then the Upgrader considers the system as up-to-date 0.382
# 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 14.367
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.952
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
40.071
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.731
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 1.932
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 20.552
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.260
After features/support/hooks.rb:326 0.665
After features/support/hooks.rb:100 0.000