Project Number Date
test_Tails_ISO_devel 3444 02 Jul 2024, 12:17

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:39.216 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:33.482
Before features/support/hooks.rb:269 0.007
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.770
When I start Tails from USB drive "old" with network unplugged 1:59.845
Then the boot device has safe access rights 2.658
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 6.864
After features/support/hooks.rb:100 0.010
Tags: @product
1:59.605
Before features/support/hooks.rb:269 0.007
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:17.749
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 30.670
And I take note of which tps features are available 1.404
Then a Tails persistence partition exists on USB drive "old" 0.779
And I shutdown Tails and wait for the computer to power off 8.478
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.010
Tags: @product
2:48.551
Before features/support/hooks.rb:269 0.007
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.670
Then Tails is running from USB drive "old" 0.318
And all tps features are active 1.928
When I write some files expected to persist 1.550
# 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.350
And all persistent directories from the old Tails version have safe access rights 2.426
And I take note of which tps features are available 0.424
And I shutdown Tails and wait for the computer to power off 4.394
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.022
After features/support/hooks.rb:326 0.098
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.051
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 10.788
And I log in to a new session 16.758
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.250
And I plug USB drive "to_upgrade" 2.361
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.042
Then the running Tails is installed on USB drive "to_upgrade" 21.465
And I unplug USB drive "to_upgrade" 0.182
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 1.776
After features/support/hooks.rb:100 0.000
Tags: @product
2:1.595
Before features/support/hooks.rb:269 0.007
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.135
Then all tps features from the old Tails version are active 1.533
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 2.929
And the expected persistent files created with the old Tails version are present in the filesystem 1.331
And all persistent directories from the old Tails version have safe access rights 2.168
After features/support/hooks.rb:326 0.661
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:15.036
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 10.590
And no SquashFS delta is installed 0.290
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.045
And Tor is ready 18.917
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.210
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.049
Given I shutdown Tails and wait for the computer to power off 8.581
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.476
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.136
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
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.320
# 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.301
When the network is plugged 0.039
And Tor is ready 19.984
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.346
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.913
Given I shutdown Tails and wait for the computer to power off 4.248
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.788
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.874
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.059
And Tor is ready 17.625
Then the Upgrader considers the system as up-to-date 0.298
# 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 13.626
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.880
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.893
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.518
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.693
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 17.629
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.556
After features/support/hooks.rb:326 0.735
After features/support/hooks.rb:100 0.000