Project Number Date
test_Tails_ISO_stable 5045 26 Aug 2024, 08:40

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:19.915 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:12.727
Before features/support/hooks.rb:269 0.007
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 34.869
When I start Tails from USB drive "old" with network unplugged 1:32.450
Then the boot device has safe access rights 3.069
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 6.910
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.187
Before features/support/hooks.rb:269 0.007
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:31.954
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 30.969
And I take note of which tps features are available 1.314
Then a Tails persistence partition exists on USB drive "old" 0.858
And I shutdown Tails and wait for the computer to power off 8.502
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.025
Before features/support/hooks.rb:269 0.008
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.346
Then Tails is running from USB drive "old" 0.382
And all tps features are active 2.262
When I write some files expected to persist 1.758
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.840
And I take note of which tps features are available 0.688
And I shutdown Tails and wait for the computer to power off 4.516
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.420
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.012
Tags: @product
2:41.072
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.919
And I log in to a new session 23.037
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.567
And I plug USB drive "to_upgrade" 2.532
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.017
Then the running Tails is installed on USB drive "to_upgrade" 24.488
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:326 2.500
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.980
Before features/support/hooks.rb:269 0.008
Given a computer 0.237
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.536
Then all tps features from the old Tails version are active 1.867
And Tails is running from USB drive "to_upgrade" 0.452
And the boot device has safe access rights 3.750
And the expected persistent files created with the old Tails version are present in the filesystem 1.557
And all persistent directories from the old Tails version have safe access rights 2.579
After features/support/hooks.rb:326 0.687
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:11.381
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 12.228
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.585
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.968
When the network is plugged 0.105
And Tor is ready 24.074
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.600
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.119
Given I shutdown Tails and wait for the computer to power off 10.869
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.280
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.388
And the file system changes introduced in version 6.2~testoverlayfs are present 0.389
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.360
# 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.304
When the network is plugged 0.071
And Tor is ready 19.504
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.355
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.282
Given I shutdown Tails and wait for the computer to power off 4.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.427
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.620
And the file system changes introduced in version 6.3~testoverlayfs are present 0.608
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.075
And Tor is ready 44.584
Then the Upgrader considers the system as up-to-date 0.393
# 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.286
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.169
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
36.540
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.699
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.842
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 17.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.026
After features/support/hooks.rb:326 0.909
After features/support/hooks.rb:100 0.000