Project Number Date
test_Tails_ISO_devel 3671 29 Jan 2025, 18:06

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:36.114 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:6.798
Before features/support/hooks.rb:269 0.002
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.478
When I start Tails from USB drive "old" with network unplugged 1:29.735
Then the boot device has safe access rights 3.218
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 3.550
After features/support/hooks.rb:100 0.019
Tags: @product
2:10.428
Before features/support/hooks.rb:269 0.024
Given a computer 0.982
And I start Tails from USB drive "old" with network unplugged and I login 1:26.789
Then Tails is running from USB drive "old" 0.385
And I create a persistent partition 31.369
And I take note of which tps features are available 1.913
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.184
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.006
Tags: @product
3:0.409
Before features/support/hooks.rb:269 0.003
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.437
Then Tails is running from USB drive "old" 0.457
And all tps features are active 2.243
When I write some files expected to persist 1.743
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.438
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.392
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.450
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.006
Tags: @product
2:36.552
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.466
And I log in to a new session 21.032
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.724
And I plug USB drive "to_upgrade" 2.499
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.157
Then the running Tails is installed on USB drive "to_upgrade" 20.233
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:326 3.883
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.595
Before features/support/hooks.rb:269 0.004
Given a computer 1.582
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.927
Then all tps features from the old Tails version are active 2.224
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.263
And the expected persistent files created with the old Tails version are present in the filesystem 1.474
And all persistent directories from the old Tails version have safe access rights 2.776
After features/support/hooks.rb:326 1.525
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:44.955
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 12.929
And no SquashFS delta is installed 0.070
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.190
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.467
When the network is plugged 0.070
And Tor is ready 19.205
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.104
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.078
Given I shutdown Tails and wait for the computer to power off 11.011
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.858
Then Tails is running version 6.2~testoverlayfs 0.036
And all tps features are active 2.807
And the file system changes introduced in version 6.2~testoverlayfs are present 0.368
And only the 6.2~testoverlayfs SquashFS delta is installed 0.135
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.579
When the network is plugged 0.084
And Tor is ready 20.029
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.731
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.629
Given I shutdown Tails and wait for the computer to power off 4.395
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.127
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.536
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.338
When the network is plugged 0.071
And Tor is ready 19.944
Then the Upgrader considers the system as up-to-date 0.356
# 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.820
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.132
After features/support/hooks.rb:326 0.975
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
39.375
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 11.465
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.456
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 20.242
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.013
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.000