Project Number Date
test_Tails_ISO_devel 3388 15 May 2024, 14:34

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 19:51.464 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.758
Before features/support/hooks.rb:259 0.006
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.142
When I start Tails from USB drive "old" with network unplugged 1:37.595
Then the boot device has safe access rights 2.823
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:305 3.505
After features/support/hooks.rb:89 0.010
Tags: @product
2:9.995
Before features/support/hooks.rb:259 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:20.489
Then Tails is running from USB drive "old" 0.385
And I create a persistent partition 38.282
And I take note of which tps features are available 1.634
Then a Tails persistence partition exists on USB drive "old" 0.824
And I shutdown Tails and wait for the computer to power off 8.210
After features/support/hooks.rb:305 0.184
After features/support/hooks.rb:89 0.010
Tags: @product
2:47.540
Before features/support/hooks.rb:259 0.007
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.474
Then Tails is running from USB drive "old" 0.335
And all tps features are active 2.058
When I write some files expected to persist 1.666
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.542
And all persistent directories from the old Tails version have safe access rights 2.683
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.554
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.386
After features/support/hooks.rb:305 0.165
After features/support/hooks.rb:89 0.011
Tags: @product
2:23.763
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.790
And I log in to a new session 18.283
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.602
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.064
Then the running Tails is installed on USB drive "to_upgrade" 15.222
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:305 6.898
After features/support/hooks.rb:89 0.000
Tags: @product
2:13.199
Before features/support/hooks.rb:259 0.005
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.361
Then all tps features from the old Tails version are active 1.666
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 2.862
And the expected persistent files created with the old Tails version are present in the filesystem 1.328
And all persistent directories from the old Tails version have safe access rights 2.502
After features/support/hooks.rb:305 0.679
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
7:31.341
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.326
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
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.489
When the network is plugged 0.039
And Tor is ready 19.434
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.153
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.264
Given I shutdown Tails and wait for the computer to power off 1:26.153
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.975
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.125
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.275
When the network is plugged 0.034
And Tor is ready 20.763
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.792
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.646
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:55.290
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.837
And the file system changes introduced in version 6.3~testoverlayfs are present 0.612
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.036
And Tor is ready 16.746
Then the Upgrader considers the system as up-to-date 0.294
# 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.556
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.949
After features/support/hooks.rb:305 0.739
After features/support/hooks.rb:89 0.016
Tags: @product @automatic_upgrade
32.864
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.993
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
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 0.489
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 15.211
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.679
After features/support/hooks.rb:305 0.876
After features/support/hooks.rb:89 0.000