The provider APIs can often change, which require updates in our code base.
We need integration tests that can notify us as soon as possible the API has changed.
Approaches that can be taken:
unit test style (only test through passive.EnumerateSubdomains)
invoke subfinder as a library
compile integration test binary, execute it and assert the output (e.g. like in nuclei)
NOTE: the API keys required for different sources should be defined as GitHub secrets and made sure they aren't visible in the logs or in any other public place.
forgedhallpass
commented
1 year ago
The provider APIs can often change, which require updates in our code base. We need integration tests that can notify us as soon as possible the API has changed.
Approaches that can be taken:
passive.EnumerateSubdomains)subfinderas a librarySources not requiring an API key:
Sources that require an API key:
NOTE: the API keys required for different sources should be defined as GitHub secrets and made sure they aren't visible in the logs or in any other public place.