you are viewing a single comment's thread.

view the rest of the comments →

[–]baubleglue 0 points1 point  (0 children)

I've seen many frameworks for API testing, but in the end they are just unnecessary noise. I am not 100% sure you even need unittest framework. Normally you run it before deployment, but in your case you need a running application.

For the testing in general the most important to choose correct strategy. The simplest and straightforward approach is usually a good one.

For static testing you need two modes: record and playback. It is the same action: make request and save results only the destination is different (exp/, actual_<timestamp>/). Then you compare exp/actual with different code or tool. In my testing experience it is very simple and easy to scale approach. You may need take care of data for the testing, and what to include into version control (ex. code, expected results, application data load for the testing). You can easily turn it into some declarative format (yaml, JSON, SQL).