Project Number Date
test_Tails_ISO_devel 3555 20 Oct 2024, 12:16

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:57.299 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:56.771
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.252
When I start Tails from USB drive "old" with network unplugged 1:22.381
Then the boot device has safe access rights 2.950
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 3.571
After features/support/hooks.rb:100 0.029
Tags: @product
2:2.239
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:20.253
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 31.218
And I take note of which tps features are available 1.230
Then a Tails persistence partition exists on USB drive "old" 0.776
And I shutdown Tails and wait for the computer to power off 8.246
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.284
Before features/support/hooks.rb:269 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.686
Then Tails is running from USB drive "old" 0.317
And all tps features are active 2.076
When I write some files expected to persist 1.584
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.358
And all persistent directories from the old Tails version have safe access rights 2.303
And I take note of which tps features are available 0.366
And I shutdown Tails and wait for the computer to power off 4.221
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.984
After features/support/hooks.rb:326 0.104
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.282
Before features/support/hooks.rb:269 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 10.417
And I log in to a new session 18.153
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.912
And I plug USB drive "to_upgrade" 2.498
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.343
Then the running Tails is installed on USB drive "to_upgrade" 20.561
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:326 3.566
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.746
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.655
Then all tps features from the old Tails version are active 1.589
And Tails is running from USB drive "to_upgrade" 0.420
And the boot device has safe access rights 3.210
And the expected persistent files created with the old Tails version are present in the filesystem 1.340
And all persistent directories from the old Tails version have safe access rights 2.354
After features/support/hooks.rb:326 0.901
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:49.181
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 12.941
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.515
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.077
And Tor is ready 22.598
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.537
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.641
Given I shutdown Tails and wait for the computer to power off 10.482
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.401
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.186
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.381
# 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.269
When the network is plugged 0.072
And Tor is ready 19.593
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.091
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.439
Given I shutdown Tails and wait for the computer to power off 4.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.087
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.131
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.070
And Tor is ready 47.872
Then the Upgrader considers the system as up-to-date 0.295
# 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.745
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.025
After features/support/hooks.rb:326 0.678
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.791
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 10.374
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 1.392
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 18.223
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.345
After features/support/hooks.rb:326 1.157
After features/support/hooks.rb:100 0.000