test(plugins): cover duplicate plugin identifier diagnostics #2168 - #2481
Open
Rakshak05 wants to merge 3 commits into
Open
test(plugins): cover duplicate plugin identifier diagnostics #2168#2481Rakshak05 wants to merge 3 commits into
Rakshak05 wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Added loader diagnostics and automated test coverage for handling duplicate plugin identifiers during plugin loading:
PluginManagerinbackend/secuscan/plugins.pyto maintain aplugin_locationsmapping of loaded plugin IDs to directory paths.load_plugins()that emits an error log identifying both conflicting plugin directory locations when a duplicate ID is encountered.test_plugin_loader_duplicate_identifier_diagnosticsintesting/backend/unit/test_plugins.pyto verify that both conflicting locations are captured in error diagnostics.Related Issues
Fixes #2168
Type of Change
How Has This Been Tested?
Executed the affected backend unit test suite using
pytest:Result: 46 passed in 2.05s (all tests passed cleanly).
Checklist