Project Number Date
test_Tails_ISO_devel 3515 13 Sep 2024, 12:38

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:25.783 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:21.683
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.042
When I start Tails from USB drive "old" with network unplugged 1:45.095
Then the boot device has safe access rights 3.143
And Tails is running from USB drive "old" 0.380
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 7.014
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.749
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:27.950
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 32.251
And I take note of which tps features are available 1.819
Then a Tails persistence partition exists on USB drive "old" 0.852
And I shutdown Tails and wait for the computer to power off 6.317
After features/support/hooks.rb:326 0.228
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.735
Before features/support/hooks.rb:269 0.004
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.313
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.359
When I write some files expected to persist 1.793
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.297
And all persistence configuration files have safe access rights 0.490
And all persistent directories from the old Tails version have safe access rights 2.340
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.193
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.892
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.559
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.515
And I log in to a new session 22.840
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.863
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.420
Then the running Tails is installed on USB drive "to_upgrade" 28.983
And I unplug USB drive "to_upgrade" 0.271
And I unplug USB drive "__internal" 0.263
After features/support/hooks.rb:326 2.177
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.887
Before features/support/hooks.rb:269 0.010
Given a computer 0.315
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.990
Then all tps features from the old Tails version are active 2.210
And Tails is running from USB drive "to_upgrade" 0.403
And the boot device has safe access rights 4.220
And the expected persistent files created with the old Tails version are present in the filesystem 1.770
And all persistent directories from the old Tails version have safe access rights 2.975
After features/support/hooks.rb:326 0.810
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:1.602
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 15.526
And no SquashFS delta is installed 0.203
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.394
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.477
When the network is plugged 0.090
And Tor is ready 19.374
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.237
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.169
Given I shutdown Tails and wait for the computer to power off 11.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.243
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 3.830
And the file system changes introduced in version 6.2~testoverlayfs are present 0.429
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.426
# 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.344
When the network is plugged 0.355
And Tor is ready 17.512
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.654
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.583
Given I shutdown Tails and wait for the computer to power off 6.743
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.527
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.098
And the file system changes introduced in version 6.3~testoverlayfs are present 0.563
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.068
And Tor is ready 17.820
Then the Upgrader considers the system as up-to-date 0.464
# 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.960
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.279
After features/support/hooks.rb:326 0.862
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
39.566
Before features/support/hooks.rb:269 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.390
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.832
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 19.789
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.005
After features/support/hooks.rb:326 1.379
After features/support/hooks.rb:100 0.000