Write functional API tests right alongside jUnit annotations
So you use jUnit, right? That's fantastic! We love jUnit and use it often ourselves for code-level unit testing.
TestServer and jUnit Side-by-Side
Test recipes written to use a supported language client library (e.g. Java, etc.) can be incorporated into jUnit testing, giving your developers a way to express their intentions not just in API code, but in tests that prove API code is functioning properly.
Unit Testing vs. Integration Testing vs. Functional Testing
Back To All Features
When a developer says that they've tested their code, often what they mean is that they've unit tested, which is to say that the most basic building blocks in code (i.e. functions, methods, members) work individually as expected. In most cases, unit testing only tests the 'happy path' of inputs and exchanges that were originally designed into the system.
Much of this testing can happen either at compile time or directly thereafter. This is an important level of testing, but does not paint a complete picture of how the system (or set of API endpoints) actually handle a real-life workflow.
When a developer performs integration testing (also consists of functional testing), this process assumes that your API is up and running somewhere, that you have an idea of how a workflow between individual pieces of code should function, and expects specific results based on variable input.
Functional testing using Ready! API TestServer means that you are well on your way to thoroughly exercising your API. Incorporate some data and inject some assertions, and you really have something to feel confident about.