Project Number Date
test_Tails_ISO_stable 4989 01 Aug 2024, 14:58

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:58.600 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:8.235
Before features/support/hooks.rb:269 0.007
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 29.136
When I start Tails from USB drive "old" with network unplugged 1:33.826
Then the boot device has safe access rights 2.958
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:326 6.958
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.467
Before features/support/hooks.rb:269 0.007
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:23.526
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 31.532
And I take note of which tps features are available 1.607
Then a Tails persistence partition exists on USB drive "old" 0.780
And I shutdown Tails and wait for the computer to power off 8.465
After features/support/hooks.rb:326 0.255
After features/support/hooks.rb:100 0.011
Tags: @product
2:58.458
Before features/support/hooks.rb:269 0.007
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.218
Then Tails is running from USB drive "old" 0.344
And all tps features are active 1.848
When I write some files expected to persist 1.699
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.744
And I take note of which tps features are available 0.376
And I shutdown Tails and wait for the computer to power off 4.406
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.951
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.662
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 10.396
And I log in to a new session 19.038
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.076
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.258
Then the running Tails is installed on USB drive "to_upgrade" 18.063
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 3.562
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.992
Before features/support/hooks.rb:269 0.007
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.308
Then all tps features from the old Tails version are active 1.508
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 3.582
And the expected persistent files created with the old Tails version are present in the filesystem 1.463
And all persistent directories from the old Tails version have safe access rights 2.658
After features/support/hooks.rb:326 1.092
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:9.813
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.264
And no SquashFS delta is installed 0.239
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.465
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.540
When the network is plugged 0.502
And Tor is ready 23.057
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.879
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.019
Given I shutdown Tails and wait for the computer to power off 9.197
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.878
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.589
And the file system changes introduced in version 6.2~testoverlayfs are present 0.354
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.383
# 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.318
When the network is plugged 0.108
And Tor is ready 17.214
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.584
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.317
Given I shutdown Tails and wait for the computer to power off 4.447
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.999
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.910
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.410
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.043
And Tor is ready 19.801
Then the Upgrader considers the system as up-to-date 0.342
# 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.559
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.060
After features/support/hooks.rb:326 0.831
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
50.970
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 24.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.394
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.853
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 20.307
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.275
After features/support/hooks.rb:326 0.702
After features/support/hooks.rb:100 0.000