Project Number Date
test_Tails_ISO_devel 3697 17 Feb 2025, 16:11

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 20:55.237 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:39.096
Before features/support/hooks.rb:269 0.006
Given a computer 0.266
And I create a 7200 MiB disk named "old" 0.088
And I plug USB drive "old" 1.091
And I write an old version of the Tails USB image to disk "old" 56.140
When I start Tails from USB drive "old" with network unplugged 1:37.368
Then the boot device has safe access rights 3.138
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.501
After features/support/hooks.rb:100 0.012
Tags: @product
2:23.431
Before features/support/hooks.rb:269 0.005
Given a computer 0.300
And I start Tails from USB drive "old" with network unplugged and I login 1:38.501
Then Tails is running from USB drive "old" 0.392
And I create a persistent partition 33.122
And I take note of which tps features are available 1.868
Then a Tails persistence partition exists on USB drive "old" 0.928
And I shutdown Tails and wait for the computer to power off 8.317
After features/support/hooks.rb:326 0.271
After features/support/hooks.rb:100 0.011
Tags: @product
3:11.441
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.700
Then Tails is running from USB drive "old" 0.437
And all tps features are active 2.412
When I write some files expected to persist 2.004
# 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.583
And all persistent directories from the old Tails version have safe access rights 2.845
And I take note of which tps features are available 0.994
And I shutdown Tails and wait for the computer to power off 4.462
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.568
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.764
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.284
And I log in to a new session 21.271
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.617
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.237
Then the running Tails is installed on USB drive "to_upgrade" 23.273
And I unplug USB drive "to_upgrade" 0.323
And I unplug USB drive "__internal" 0.270
After features/support/hooks.rb:326 2.503
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.188
Before features/support/hooks.rb:269 0.007
Given a computer 1.286
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.418
Then all tps features from the old Tails version are active 1.865
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.409
And the expected persistent files created with the old Tails version are present in the filesystem 1.903
And all persistent directories from the old Tails version have safe access rights 2.915
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:1.507
Before features/support/hooks.rb:269 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.471
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.440
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.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.520
When the network is plugged 0.070
And Tor is ready 19.388
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.686
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.023
Given I shutdown Tails and wait for the computer to power off 8.646
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.749
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.716
And the file system changes introduced in version 6.2~testoverlayfs are present 0.381
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.322
When the network is plugged 0.082
And Tor is ready 18.603
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.985
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.213
Given I shutdown Tails and wait for the computer to power off 6.851
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.370
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.191
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.476
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.338
When the network is plugged 0.079
And Tor is ready 18.328
Then the Upgrader considers the system as up-to-date 10.779
# 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 16.320
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.926
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.808
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 10.481
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
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.072
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.724
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.993
After features/support/hooks.rb:326 0.871
After features/support/hooks.rb:100 0.000