Challenge Overview
Previously, we have documented the API specification for Billing Account Related APIs (attached in forum) using swagger.
For this challenge, we'd like to see a good way to mock the apis, so we can start out integration even without the detail impelementation is ready.
Following are the requirements:
1. The mock apis should cover valid and invalid cases.
2. The data is not required to be dynamically, but it should reach that for different api request, it returns the same valid or invalid result.
3. The mock service should be easily to change, as we definitely will update the mock service to
3.1 Update the api request pattern
3.2 Update the api response
3.3 Add New apis
3.4 etc
So the mock service should be flexiable to make changes, this is an important consideration for review and scoring.
4. Please properly document the each request and expected result for integration consideration
- Documentation About the request and expected result
For this challenge, we'd like to see a good way to mock the apis, so we can start out integration even without the detail impelementation is ready.
Following are the requirements:
1. The mock apis should cover valid and invalid cases.
2. The data is not required to be dynamically, but it should reach that for different api request, it returns the same valid or invalid result.
3. The mock service should be easily to change, as we definitely will update the mock service to
3.1 Update the api request pattern
3.2 Update the api response
3.3 Add New apis
3.4 etc
So the mock service should be flexiable to make changes, this is an important consideration for review and scoring.
4. Please properly document the each request and expected result for integration consideration
Final Submission Guidelines
- Mock Service Implementation- Documentation About the request and expected result