Right now we are calling the real intake for the functional tests of Gradle Plugin, and since we don’t have a real API key, we get an error and we expect build failure in our tests. However, it may be some other build failures, so it is handy to emulate network call to make test expectation without any build failures.
This PR adds build parameter dd-emulate-upload-call which can be passed for the build script execution. If it is present, no real network call will be made and we will create a fake response.
Review checklist (to be filled by reviewers)
[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)
What does this PR do?
Right now we are calling the real intake for the functional tests of Gradle Plugin, and since we don’t have a real API key, we get an error and we expect build failure in our tests. However, it may be some other build failures, so it is handy to emulate network call to make test expectation without any build failures.
This PR adds build parameter
dd-emulate-upload-call
which can be passed for the build script execution. If it is present, no real network call will be made and we will create a fake response.Review checklist (to be filled by reviewers)