Project Number Date
test_Tails_ISO_stable 5291 25 Nov 2024, 20:04

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 21:48.386 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:16.428
Before features/support/hooks.rb:269 0.006
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.026
When I start Tails from USB drive "old" with network unplugged 1:38.706
Then the boot device has safe access rights 3.368
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:326 3.766
After features/support/hooks.rb:100 0.011
Tags: @product
2:21.670
Before features/support/hooks.rb:269 0.009
Given a computer 0.375
And I start Tails from USB drive "old" with network unplugged and I login 1:35.421
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 34.709
And I take note of which tps features are available 1.508
Then a Tails persistence partition exists on USB drive "old" 0.895
And I shutdown Tails and wait for the computer to power off 8.411
After features/support/hooks.rb:326 0.214
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.802
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.803
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.107
When I write some files expected to persist 2.068
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.446
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 4.312
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.476
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.541
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.744
And I log in to a new session 20.575
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.505
And I plug USB drive "to_upgrade" 2.609
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.328
Then the running Tails is installed on USB drive "to_upgrade" 20.334
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 7.273
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.034
Before features/support/hooks.rb:269 0.006
Given a computer 0.237
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.723
Then all tps features from the old Tails version are active 1.745
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.566
And the expected persistent files created with the old Tails version are present in the filesystem 1.628
And all persistent directories from the old Tails version have safe access rights 2.764
After features/support/hooks.rb:326 1.035
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
8:25.609
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 13.349
And no SquashFS delta is installed 0.636
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.352
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.567
When the network is plugged 0.064
And Tor is ready 51.516
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.587
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.530
Given I shutdown Tails and wait for the computer to power off 1:21.590
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.799
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.446
And the file system changes introduced in version 6.2~testoverlayfs are present 0.491
And only the 6.2~testoverlayfs SquashFS delta is installed 0.173
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.480
# 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.437
When the network is plugged 0.105
And Tor is ready 19.663
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.563
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.873
Given I shutdown Tails and wait for the computer to power off 6.664
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.014
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.644
And the file system changes introduced in version 6.3~testoverlayfs are present 0.589
And only the 6.3~testoverlayfs SquashFS delta is installed 0.112
# 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.426
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.320
When the network is plugged 0.073
And Tor is ready 21.018
Then the Upgrader considers the system as up-to-date 0.322
# 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.586
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.095
After features/support/hooks.rb:326 0.799
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
43.298
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.179
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.766
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.797
But a current signing key is available on our website 0.000
When the network is plugged 0.167
And Tor is ready 25.131
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.196
After features/support/hooks.rb:326 0.645
After features/support/hooks.rb:100 0.000