Project Number Date
test_Tails_ISO_devel 3435 21 Jun 2024, 12:48

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:43.403 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:24.244
Before features/support/hooks.rb:269 0.007
Given a computer 0.234
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.997
When I start Tails from USB drive "old" with network unplugged 1:46.515
Then the boot device has safe access rights 3.331
And Tails is running from USB drive "old" 0.400
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 3.586
After features/support/hooks.rb:100 0.011
Tags: @product
2:0.687
Before features/support/hooks.rb:269 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:18.751
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 30.946
And I take note of which tps features are available 1.391
Then a Tails persistence partition exists on USB drive "old" 0.778
And I shutdown Tails and wait for the computer to power off 8.265
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.012
Tags: @product
2:48.577
Before features/support/hooks.rb:269 0.007
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.211
Then Tails is running from USB drive "old" 0.357
And all tps features are active 2.208
When I write some files expected to persist 1.604
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.488
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.255
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.060
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.519
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.610
And I log in to a new session 17.832
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.429
And I plug USB drive "to_upgrade" 2.381
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.806
Then the running Tails is installed on USB drive "to_upgrade" 22.065
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 3.628
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.183
Before features/support/hooks.rb:269 0.008
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.005
Then all tps features from the old Tails version are active 1.615
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.092
And the expected persistent files created with the old Tails version are present in the filesystem 1.559
And all persistent directories from the old Tails version have safe access rights 2.346
After features/support/hooks.rb:326 0.643
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:13.698
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.080
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
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.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.059
And Tor is ready 20.992
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.323
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.111
Given I shutdown Tails and wait for the computer to power off 8.585
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.934
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.113
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
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.371
# 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.237
When the network is plugged 0.045
And Tor is ready 16.784
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.975
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.304
Given I shutdown Tails and wait for the computer to power off 4.381
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.161
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.115
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
And only the 6.3~testoverlayfs SquashFS delta is installed 0.106
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.036
And Tor is ready 17.147
Then the Upgrader considers the system as up-to-date 0.296
# 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.830
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.923
After features/support/hooks.rb:326 0.757
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
33.492
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.428
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.823
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 17.963
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.872
After features/support/hooks.rb:326 0.635
After features/support/hooks.rb:100 0.000