Project Number Date
test_Tails_ISO_devel 3717 03 Mar 2025, 22:36

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:12.189 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:9.874
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 33.493
When I start Tails from USB drive "old" with network unplugged 1:30.968
Then the boot device has safe access rights 3.058
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 3.793
After features/support/hooks.rb:100 0.020
Tags: @product
2:5.013
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:22.904
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 30.314
And I take note of which tps features are available 2.018
Then a Tails persistence partition exists on USB drive "old" 0.774
And I shutdown Tails and wait for the computer to power off 8.445
After features/support/hooks.rb:330 0.274
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.223
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.570
Then Tails is running from USB drive "old" 0.360
And all tps features are active 2.047
When I write some files expected to persist 1.807
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.598
And all persistent directories from the old Tails version have safe access rights 2.627
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.441
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.838
After features/support/hooks.rb:330 0.107
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.954
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.986
And I log in to a new session 18.782
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.418
And I plug USB drive "to_upgrade" 2.542
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.820
Then the running Tails is installed on USB drive "to_upgrade" 16.921
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.270
After features/support/hooks.rb:330 1.851
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.206
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.470
Then all tps features from the old Tails version are active 1.724
And Tails is running from USB drive "to_upgrade" 0.409
And the boot device has safe access rights 3.316
And the expected persistent files created with the old Tails version are present in the filesystem 1.653
And all persistent directories from the old Tails version have safe access rights 2.446
After features/support/hooks.rb:330 1.011
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
7:20.791
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.555
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.580
When the network is plugged 0.093
And Tor is ready 50.432
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.632
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.979
Given I shutdown Tails and wait for the computer to power off 8.740
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.108
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.226
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.275
When the network is plugged 0.067
And Tor is ready 18.085
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.468
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.070
Given I shutdown Tails and wait for the computer to power off 4.400
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.118
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.341
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.069
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.365
When the network is plugged 0.065
And Tor is ready 18.505
Then the Upgrader considers the system as up-to-date 0.305
# 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.971
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.970
After features/support/hooks.rb:330 0.741
After features/support/hooks.rb:100 0.065
Tags: @product @automatic_upgrade
57.124
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.567
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.535
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.065
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 46.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.588
After features/support/hooks.rb:330 0.910
After features/support/hooks.rb:100 0.000