Your unit tests mock the database, the queue or the downstream service. That proves your code made the call. It doesn't prove the row, the message or the request ever got there.
API Test Base tests the API with its real dependencies attached. Call the endpoint, then go and look: query the table, read the message off the queue, check what the downstream service was actually sent, and assert on what's really there.
Test cases are YAML files you author in a desktop app, keep in Git, and run the same way on your laptop and in your CI/CD pipeline.
Free, offline, no account.
Supported protocols: HTTP, SOAP, relational databases (Oracle, SQL Server, PostgreSQL, H2 and others), JMS (ActiveMQ, Solace), IBM MQ, AMQP, MQTT, FTP(S), SFTP, local files, and IBM App Connect Enterprise (ACE, formerly IIB).
Comments, support and feedback
- Zheng Wanga month agoMaker
Thanks Joseph, glad it looked useful — and worth adding what happens after the response comes back. API Test Base goes and checks the API's side effects, i.e. the state in the API's dependencies: the row actually landed in the database, the message actually reached the queue, the downstream API was actually called with the expected request. That's the bit a mocked test can't see.
- 2 months ago
API Test Base is a simple and useful tool for testing APIs quickly, helping developers check requests, responses, and improve workflow efficiency.
About this launch
API Test Base by Zheng Wang Will be launched July 13th 2027.