Project Number Date
test_Tails_ISO_stable 5360 29 Dec 2024, 12:15

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:34.207 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:12.696
Before features/support/hooks.rb:269 0.005
Given a computer 0.248
And I create a 7200 MiB disk named "old" 0.072
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 28.902
When I start Tails from USB drive "old" with network unplugged 1:38.513
Then the boot device has safe access rights 2.867
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.472
After features/support/hooks.rb:100 0.025
Tags: @product
2:3.824
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:22.080
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 30.565
And I take note of which tps features are available 1.463
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.405
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.699
Before features/support/hooks.rb:269 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.455
Then Tails is running from USB drive "old" 0.976
And all tps features are active 1.988
When I write some files expected to persist 1.840
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.419
And all persistence configuration files have safe access rights 0.479
And all persistent directories from the old Tails version have safe access rights 3.298
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 4.402
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.092
After features/support/hooks.rb:326 0.083
After features/support/hooks.rb:100 0.007
Tags: @product
2:26.220
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.517
And I log in to a new session 20.369
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.834
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.386
Then the running Tails is installed on USB drive "to_upgrade" 17.281
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 6.861
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.513
Before features/support/hooks.rb:269 0.006
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.321
Then all tps features from the old Tails version are active 1.656
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 3.234
And the expected persistent files created with the old Tails version are present in the filesystem 1.498
And all persistent directories from the old Tails version have safe access rights 2.284
After features/support/hooks.rb:326 0.682
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:11.415
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 12.302
And no SquashFS delta is installed 0.154
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.080
And Tor is ready 19.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.766
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.791
Given I shutdown Tails and wait for the computer to power off 10.637
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.194
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.060
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.260
When the network is plugged 0.091
And Tor is ready 17.586
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.428
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.617
Given I shutdown Tails and wait for the computer to power off 4.296
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.971
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.219
And the file system changes introduced in version 6.3~testoverlayfs are present 0.449
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.071
And Tor is ready 18.469
Then the Upgrader considers the system as up-to-date 0.311
# 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 13.875
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.999
After features/support/hooks.rb:326 0.816
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.836
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 10.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
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.071
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 20.115
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.168
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.000