Project Number Date
test_Tails_ISO_stable 4705 10 Mar 2024, 12:07

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:13.851 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
1:33.671
Before features/support/hooks.rb:245 0.005
Given a computer 0.153
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 22.000
When I start Tails from USB drive "old" with network unplugged 1:6.407
Then the boot device has safe access rights 2.893
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.137
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:291 3.536
After features/support/hooks.rb:75 0.097
Tags: @product
2:5.361
Before features/support/hooks.rb:245 0.006
Given a computer 0.152
And I start Tails from USB drive "old" with network unplugged and I login 1:14.706
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 40.705
And I take note of which tps features are available 1.803
Then a Tails persistence partition exists on USB drive "old" 0.650
And I shutdown Tails and wait for the computer to power off 7.021
After features/support/hooks.rb:291 0.148
After features/support/hooks.rb:75 0.010
Tags: @product
2:37.888
Before features/support/hooks.rb:245 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.413
Then Tails is running from USB drive "old" 0.312
And all tps features are active 1.688
When I write some files expected to persist 1.678
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.373
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.368
And I shutdown Tails and wait for the computer to power off 4.215
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.981
After features/support/hooks.rb:291 0.115
After features/support/hooks.rb:75 0.009
Tags: @product
2:32.461
Before features/support/hooks.rb:245 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 9.524
And I log in to a new session 17.750
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.456
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.441
Then the running Tails is installed on USB drive "to_upgrade" 13.379
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.295
After features/support/hooks.rb:291 3.576
After features/support/hooks.rb:75 0.000
Tags: @product
2:20.659
Before features/support/hooks.rb:245 0.006
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.405
Then all tps features from the old Tails version are active 1.346
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.284
And the expected persistent files created with the old Tails version are present in the filesystem 1.467
And all persistent directories from the old Tails version have safe access rights 2.604
After features/support/hooks.rb:291 0.722
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
6:31.296
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.096
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.030
And Tor is ready 18.218
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.826
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.386
Given I shutdown Tails and wait for the computer to power off 6.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.672
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.780
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.317
When the network is plugged 0.033
And Tor is ready 15.549
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.799
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.492
Given I shutdown Tails and wait for the computer to power off 4.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.915
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.805
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.037
And Tor is ready 17.941
Then the Upgrader considers the system as up-to-date 0.253
# 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 12.753
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.147
After features/support/hooks.rb:291 0.809
After features/support/hooks.rb:75 0.029
Tags: @product @automatic_upgrade
32.511
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.481
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 16.111
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.382
After features/support/hooks.rb:291 0.770
After features/support/hooks.rb:75 0.000