API Testing for fprdata

Overview
As part of Testing Culture initiative, flight system team has been implementing API testing for fprdata service. The API testing is already integrated with auto-deployment in staging. Since most of the features in fprdata are managed and owned by the subdomain team, the API testing also will be part of the subdomain team responsibilities.

To keep the API testing relevant and bring benefits to the whole flight team, starting 1st April 2021 we'll roll out a new policy in fprdata with the following details.

API Testing for new features is mandatory, the flight system will reject the PR about a new feature (new servlet URL path or new method) that doesn't include API tests.
Subdomain team responsible to maintain the API tests.
Subdomain team is not allowed to deploy fprdata to production if the API testing fails.

To roll out successfully the new policy above, we highly recommend the subdomain team starting to use API testing and monitor its result.

Notes

The API tests for fprdata is located at here.
The API tests result is reported to the channel #flight-system-api-testing-report.