prowler-test-sdk

To write unit tests for Prowler SDK security checks, use provider-specific mocking strategies: implement moto for AWS services and MagicMock for Azure and GCP to accurately simulate compliant and non-compliant configurations.

The best way to mock AWS services for Prowler testing is using the moto library, which allows you to simulate AWS resource states and verify that your security checks correctly identify compliant, non-compliant, and no-resource scenarios.

Yes, you can use MagicMock for testing Azure and GCP security checks in the Prowler SDK. It provides the necessary mocking patterns to simulate provider responses and validate check logic without actual cloud connections.

When testing Prowler security checks, you should cover three essential test scenarios: compliant resources, non-compliant resources, and no-resource cases. This ensures your check logic handles all states accurately and reliably.

To structure test files for Prowler SDK checks, follow the provided testing patterns that organize test cases by provider and check logic, ensuring maintainable unit tests that validate compliant and non-compliant configurations effectively.