Project Number Date
test_Tails_ISO_stable 5086 09 Sep 2024, 15:03

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:27.521 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:17.882
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 31.923
When I start Tails from USB drive "old" with network unplugged 1:40.190
Then the boot device has safe access rights 3.351
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.372
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:326 3.546
After features/support/hooks.rb:100 0.026
Tags: @product
2:10.928
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:23.614
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 34.231
And I take note of which tps features are available 2.653
Then a Tails persistence partition exists on USB drive "old" 0.954
And I shutdown Tails and wait for the computer to power off 8.938
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.063
Before features/support/hooks.rb:269 0.007
Given a computer 0.392
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.361
Then Tails is running from USB drive "old" 0.311
And all tps features are active 2.027
When I write some files expected to persist 1.752
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.307
And all persistence configuration files have safe access rights 0.540
And all persistent directories from the old Tails version have safe access rights 2.430
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.385
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.060
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.792
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 14.926
And I log in to a new session 19.774
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.894
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.661
Then the running Tails is installed on USB drive "to_upgrade" 18.700
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 3.618
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.618
Before features/support/hooks.rb:269 0.008
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.978
Then all tps features from the old Tails version are active 2.052
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.692
And the expected persistent files created with the old Tails version are present in the filesystem 1.610
And all persistent directories from the old Tails version have safe access rights 2.715
After features/support/hooks.rb:326 0.851
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:19.545
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 42.729
And no SquashFS delta is installed 0.213
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.474
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.177
And Tor is ready 28.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.607
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.150
Given I shutdown Tails and wait for the computer to power off 8.960
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.793
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.750
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.267
When the network is plugged 0.079
And Tor is ready 21.545
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.235
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.647
Given I shutdown Tails and wait for the computer to power off 4.489
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.677
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.705
And the file system changes introduced in version 6.3~testoverlayfs are present 0.564
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.404
When the network is plugged 0.090
And Tor is ready 15.676
Then the Upgrader considers the system as up-to-date 0.387
# 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.886
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.352
After features/support/hooks.rb:326 1.088
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
39.689
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.443
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 1.024
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 21.078
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.555
After features/support/hooks.rb:326 1.232
After features/support/hooks.rb:100 0.000