Project Number Date
test_Tails_ISO_devel 3598 24 Nov 2024, 12:53

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:47.164 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:27.672
Before features/support/hooks.rb:269 0.009
Given a computer 0.255
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.071
And I write an old version of the Tails USB image to disk "old" 37.329
When I start Tails from USB drive "old" with network unplugged 1:44.534
Then the boot device has safe access rights 3.334
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.126
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:326 4.042
After features/support/hooks.rb:100 0.012
Tags: @product
2:18.010
Before features/support/hooks.rb:269 0.009
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:31.169
Then Tails is running from USB drive "old" 0.480
And I create a persistent partition 34.583
And I take note of which tps features are available 1.721
Then a Tails persistence partition exists on USB drive "old" 0.919
And I shutdown Tails and wait for the computer to power off 8.899
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.811
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.748
Then Tails is running from USB drive "old" 1.628
And all tps features are active 2.681
When I write some files expected to persist 1.939
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.267
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 2.640
And I take note of which tps features are available 0.631
And I shutdown Tails and wait for the computer to power off 4.455
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.181
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.012
Tags: @product
3:6.654
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 31.375
And I log in to a new session 21.915
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.308
And I plug USB drive "to_upgrade" 2.601
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.293
Then the running Tails is installed on USB drive "to_upgrade" 22.714
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 3.352
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.540
Before features/support/hooks.rb:269 0.007
Given a computer 0.336
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.130
Then all tps features from the old Tails version are active 1.885
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.602
And the expected persistent files created with the old Tails version are present in the filesystem 2.532
And all persistent directories from the old Tails version have safe access rights 2.713
After features/support/hooks.rb:326 1.143
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:50.598
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 14.133
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.356
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.570
When the network is plugged 0.080
And Tor is ready 20.449
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.287
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.400
Given I shutdown Tails and wait for the computer to power off 11.120
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.392
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.326
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.291
When the network is plugged 0.072
And Tor is ready 21.037
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.500
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.874
Given I shutdown Tails and wait for the computer to power off 4.596
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.300
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.285
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.150
# 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.370
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.092
And Tor is ready 19.218
Then the Upgrader considers the system as up-to-date 10.832
# 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.638
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.193
After features/support/hooks.rb:326 0.810
After features/support/hooks.rb:100 0.072
Tags: @product @automatic_upgrade
39.876
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 11.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.839
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 20.702
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.659
After features/support/hooks.rb:326 0.701
After features/support/hooks.rb:100 0.000