Project Number Date
test_Tails_ISO_devel 3660 24 Jan 2025, 17:50

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:46.961 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.404
Before features/support/hooks.rb:269 0.003
Given a computer 0.829
And I create a 7200 MiB disk named "old" 0.191
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.534
When I start Tails from USB drive "old" with network unplugged 1:27.511
Then the boot device has safe access rights 3.192
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.233
After features/support/hooks.rb:326 3.816
After features/support/hooks.rb:100 0.006
Tags: @product
2:11.328
Before features/support/hooks.rb:269 0.003
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:27.379
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 32.530
And I take note of which tps features are available 1.506
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.560
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.006
Tags: @product
2:49.168
Before features/support/hooks.rb:269 0.003
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.853
Then Tails is running from USB drive "old" 0.599
And all tps features are active 2.122
When I write some files expected to persist 1.847
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.790
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.231
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.434
After features/support/hooks.rb:326 0.101
After features/support/hooks.rb:100 0.006
Tags: @product
2:31.167
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.694
And I log in to a new session 19.382
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.536
And I plug USB drive "to_upgrade" 2.388
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.815
Then the running Tails is installed on USB drive "to_upgrade" 20.940
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 2.374
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.712
Before features/support/hooks.rb:269 0.003
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.096
Then all tps features from the old Tails version are active 1.570
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 3.227
And the expected persistent files created with the old Tails version are present in the filesystem 1.749
And all persistent directories from the old Tails version have safe access rights 2.592
After features/support/hooks.rb:326 1.172
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
6:28.131
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.209
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.109
And Tor is ready 19.486
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.332
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.731
Given I shutdown Tails and wait for the computer to power off 8.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.160
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.600
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.334
When the network is plugged 0.063
And Tor is ready 19.554
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.050
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.657
Given I shutdown Tails and wait for the computer to power off 4.240
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.627
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.066
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.065
And Tor is ready 17.587
Then the Upgrader considers the system as up-to-date 0.317
# 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 15.460
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.034
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
36.049
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.890
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the signing key used by the Upgrader is outdated 0.125
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 20.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.885
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.000