Project Number Date
test_Tails_ISO_devel 3626 29 Dec 2024, 12:25

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 19:21.925 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:4.538
Before features/support/hooks.rb:269 0.006
Given a computer 0.236
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.219
When I start Tails from USB drive "old" with network unplugged 1:29.054
Then the boot device has safe access rights 2.926
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.528
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.454
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:21.103
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 30.306
And I take note of which tps features are available 1.550
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 8.202
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.477
Before features/support/hooks.rb:269 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.000
Then Tails is running from USB drive "old" 0.346
And all tps features are active 2.300
When I write some files expected to persist 1.646
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 2.367
And I take note of which tps features are available 0.533
And I shutdown Tails and wait for the computer to power off 4.155
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.222
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.719
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 11.220
And I log in to a new session 18.530
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.785
And I plug USB drive "to_upgrade" 2.431
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.494
Then the running Tails is installed on USB drive "to_upgrade" 20.838
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.020
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.619
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.461
Then all tps features from the old Tails version are active 1.612
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.255
And the expected persistent files created with the old Tails version are present in the filesystem 1.382
And all persistent directories from the old Tails version have safe access rights 2.373
After features/support/hooks.rb:326 1.019
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:2.196
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 25.726
And no SquashFS delta is installed 0.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.075
And Tor is ready 17.542
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.723
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.548
Given I shutdown Tails and wait for the computer to power off 8.502
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.505
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.183
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.125
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.321
When the network is plugged 0.072
And Tor is ready 18.516
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.491
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.513
Given I shutdown Tails and wait for the computer to power off 4.272
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.095
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.153
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.060
And Tor is ready 48.849
Then the Upgrader considers the system as up-to-date 0.308
# 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.424
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.009
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
33.919
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.894
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.752
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 15.242
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.639
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.000