feat: end-to-end api test #145
Description
Is your feature request related to a problem? Please describe.
We are currently having a bunch of API and we might have more in the future. For each feature there might be more advancement and there will also be more feature to develop later on.
When updating an API flow (adding with a new functionality or support new behaviour), we need to make sure that it won't break any flow other than the updated one. So far, we check and test the API manually when we are dealing with that problem. To save some time, we need to automate the end-to-end API test at least to avoid regression error.
In our current compass version, we have a sample of end to end test in package /test/e2e_test, back then it was being used to test when major changes happened (renaming from columbus to compass, moving assets to postgres, etc). However, that was not a long term solution and there might be a better approach to do so.
Describe the solution you'd like
- We need to analyze how is the best way to implement end-to-end API test in compass
- Breaking down the scenario that are needed to test
- Implement the end-to-end API test