Project Number Date
test_Tails_ISO_stable 5156 08 Oct 2024, 08:59

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:6.329 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.094
Before features/support/hooks.rb:269 0.005
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 30.845
When I start Tails from USB drive "old" with network unplugged 1:35.464
Then the boot device has safe access rights 3.409
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:326 7.170
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.350
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:31.440
Then Tails is running from USB drive "old" 0.412
And I create a persistent partition 31.332
And I take note of which tps features are available 1.880
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 6.222
After features/support/hooks.rb:326 0.214
After features/support/hooks.rb:100 0.007
Tags: @product
3:3.314
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.800
Then Tails is running from USB drive "old" 1.639
And all tps features are active 2.288
When I write some files expected to persist 3.831
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 3.648
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.368
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.355
After features/support/hooks.rb:326 0.089
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.617
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.458
And I log in to a new session 19.780
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.675
And I plug USB drive "to_upgrade" 2.500
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.471
Then the running Tails is installed on USB drive "to_upgrade" 24.332
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 2.218
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.257
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.688
Then all tps features from the old Tails version are active 2.466
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 3.435
And the expected persistent files created with the old Tails version are present in the filesystem 1.533
And all persistent directories from the old Tails version have safe access rights 2.546
After features/support/hooks.rb:326 0.758
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:4.812
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 16.991
And no SquashFS delta is installed 0.264
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.514
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.509
When the network is plugged 0.238
And Tor is ready 20.172
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.748
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.293
Given I shutdown Tails and wait for the computer to power off 8.949
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.481
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.451
And the file system changes introduced in version 6.2~testoverlayfs are present 0.371
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.335
# 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.297
When the network is plugged 0.078
And Tor is ready 17.299
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.397
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.006
Given I shutdown Tails and wait for the computer to power off 4.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.004
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.393
And the file system changes introduced in version 6.3~testoverlayfs are present 0.536
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.355
When the network is plugged 0.081
And Tor is ready 47.681
Then the Upgrader considers the system as up-to-date 0.349
# 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.683
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.102
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
39.882
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.535
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.375
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.885
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 21.641
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.270
After features/support/hooks.rb:326 0.840
After features/support/hooks.rb:100 0.000