Project Number Date
test_Tails_ISO_stable 5036 19 Aug 2024, 19:02

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:45.769 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:48.165
Before features/support/hooks.rb:269 0.006
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 1:11.488
When I start Tails from USB drive "old" with network unplugged 1:31.012
Then the boot device has safe access rights 3.258
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 7.221
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.569
Before features/support/hooks.rb:269 0.007
Given a computer 0.273
And I start Tails from USB drive "old" with network unplugged and I login 1:29.881
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 32.329
And I take note of which tps features are available 1.937
Then a Tails persistence partition exists on USB drive "old" 0.978
And I shutdown Tails and wait for the computer to power off 8.810
After features/support/hooks.rb:326 0.224
After features/support/hooks.rb:100 0.012
Tags: @product
3:14.820
Before features/support/hooks.rb:269 0.007
Given a computer 0.284
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.023
Then Tails is running from USB drive "old" 0.371
And all tps features are active 2.295
When I write some files expected to persist 1.737
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 3.076
And I take note of which tps features are available 0.526
And I shutdown Tails and wait for the computer to power off 4.824
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.059
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.013
Tags: @product
2:39.708
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 13.331
And I log in to a new session 22.587
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.627
And I plug USB drive "to_upgrade" 2.518
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.015
Then the running Tails is installed on USB drive "to_upgrade" 22.107
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.302
After features/support/hooks.rb:326 3.422
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.658
Before features/support/hooks.rb:269 0.007
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.896
Then all tps features from the old Tails version are active 1.834
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.389
And the expected persistent files created with the old Tails version are present in the filesystem 1.573
And all persistent directories from the old Tails version have safe access rights 2.406
After features/support/hooks.rb:326 0.597
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:48.228
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 15.007
And no SquashFS delta is installed 0.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.120
And Tor is ready 20.639
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.742
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.429
Given I shutdown Tails and wait for the computer to power off 8.694
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.780
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 3.511
And the file system changes introduced in version 6.2~testoverlayfs are present 0.415
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.318
When the network is plugged 0.075
And Tor is ready 18.573
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.629
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.489
Given I shutdown Tails and wait for the computer to power off 4.535
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.152
Then Tails is running version 6.3~testoverlayfs 0.032
And all tps features are active 2.030
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.377
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.089
And Tor is ready 19.034
Then the Upgrader considers the system as up-to-date 0.349
# 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.429
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.077
After features/support/hooks.rb:326 0.822
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
39.617
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.444
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.661
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 1.324
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 19.672
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.382
After features/support/hooks.rb:326 0.882
After features/support/hooks.rb:100 0.000