Project Number Date
test_Tails_ISO_devel 3565 28 Oct 2024, 15:27

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:13.443 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.196
Before features/support/hooks.rb:269 0.007
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.123
And I write an old version of the Tails USB image to disk "old" 30.441
When I start Tails from USB drive "old" with network unplugged 1:35.064
Then the boot device has safe access rights 4.039
And Tails is running from USB drive "old" 0.461
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.363
And I unplug USB drive "old" 0.258
After features/support/hooks.rb:326 7.457
After features/support/hooks.rb:100 0.011
Tags: @product
2:14.781
Before features/support/hooks.rb:269 0.008
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login 1:32.047
Then Tails is running from USB drive "old" 0.452
And I create a persistent partition 31.543
And I take note of which tps features are available 2.949
Then a Tails persistence partition exists on USB drive "old" 0.911
And I shutdown Tails and wait for the computer to power off 6.634
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.013
Tags: @product
2:58.813
Before features/support/hooks.rb:269 0.008
Given a computer 0.491
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.357
Then Tails is running from USB drive "old" 0.389
And all tps features are active 2.116
When I write some files expected to persist 1.920
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.945
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.627
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.813
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:38.908
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.263
And I log in to a new session 21.254
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.907
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.147
Then the running Tails is installed on USB drive "to_upgrade" 22.227
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.448
After features/support/hooks.rb:326 2.282
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.898
Before features/support/hooks.rb:269 0.009
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.323
Then all tps features from the old Tails version are active 1.635
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.555
And the expected persistent files created with the old Tails version are present in the filesystem 1.410
And all persistent directories from the old Tails version have safe access rights 2.413
After features/support/hooks.rb:326 1.138
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:4.260
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 12.927
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.070
And Tor is ready 24.839
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.679
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.652
Given I shutdown Tails and wait for the computer to power off 10.817
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.605
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.408
And the file system changes introduced in version 6.2~testoverlayfs are present 0.436
And only the 6.2~testoverlayfs SquashFS delta is installed 0.149
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.372
# 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.401
When the network is plugged 0.530
And Tor is ready 47.178
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.596
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.231
Given I shutdown Tails and wait for the computer to power off 4.133
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.441
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 4.670
And the file system changes introduced in version 6.3~testoverlayfs are present 0.570
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.070
And Tor is ready 14.468
Then the Upgrader considers the system as up-to-date 0.334
# 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 16.037
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.393
After features/support/hooks.rb:326 1.010
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
47.583
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 15.453
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.159
And the signing key used by the Upgrader is outdated 1.136
But a current signing key is available on our website 0.000
When the network is plugged 0.109
And Tor is ready 22.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.858
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.000