Project Number Date
test_Tails_ISO_devel 3589 16 Nov 2024, 12:42

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:49.469 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.537
Before features/support/hooks.rb:269 0.006
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 34.002
When I start Tails from USB drive "old" with network unplugged 1:25.174
Then the boot device has safe access rights 3.076
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.236
After features/support/hooks.rb:326 9.044
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.307
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:20.170
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 32.080
And I take note of which tps features are available 1.493
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 8.247
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.733
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.769
Then Tails is running from USB drive "old" 0.363
And all tps features are active 1.865
When I write some files expected to persist 1.647
# 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.367
And all persistent directories from the old Tails version have safe access rights 2.191
And I take note of which tps features are available 0.380
And I shutdown Tails and wait for the computer to power off 4.355
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.361
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.847
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.641
And I log in to a new session 18.178
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.853
And I plug USB drive "to_upgrade" 2.466
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.931
Then the running Tails is installed on USB drive "to_upgrade" 22.367
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 3.615
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.218
Before features/support/hooks.rb:269 0.006
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.149
Then all tps features from the old Tails version are active 1.810
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.078
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.290
After features/support/hooks.rb:326 1.155
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:20.395
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 11.674
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.548
When the network is plugged 0.073
And Tor is ready 21.526
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.747
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.820
Given I shutdown Tails and wait for the computer to power off 8.382
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.042
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.249
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.079
And Tor is ready 19.685
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.368
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.740
Given I shutdown Tails and wait for the computer to power off 4.219
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.038
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.028
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.084
And Tor is ready 19.600
Then the Upgrader considers the system as up-to-date 0.299
# 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.067
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.087
After features/support/hooks.rb:326 0.730
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.429
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 10.545
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.068
And the signing key used by the Upgrader is outdated 0.915
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 18.086
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.441
After features/support/hooks.rb:326 0.646
After features/support/hooks.rb:100 0.000