CredentialValidationFailed: Unable to authenticate with endpoint X in NPSS integration test harness
0 reputation · 15 Jul 2026, 14:12 UTC
Run NPSS integration tests using the test harness without providing production credentials, relying on mock credential objects to validate component interactions.
The test harness throws the error CredentialValidationFailed: Unable to authenticate with endpoint X when credentials are invalid. It is unresolved whether the harness should automatically fall back to a simulated service in this scenario or require an explicit test‑mode flag such as NPSS_TEST_MODE, especially since the fallback behavior differs between NPSS 3.2 (silent proceed with default mock data) and NPSS 3.4 (abort unless the flag is set).
Should the NPSS test harness automatically fall back to a simulated service when credential validation fails, or should it mandate an explicit test‑mode flag? How should the version‑specific fallback behavior be documented to ensure consistent test outcomes across installations? What environment variable or configuration option should control this fallback behavior uniformly?
npss