API Testing
API testing is a process that confirms an API is working as expected. There are several types of API tests, and each one plays a distinct role in ensuring that the API’s functionality, security, and performance remain reliable. Developers can run API tests manually, or they can automate them with an API testing tool.
Developers use API’s as one simply breathes – it is a requirement to be productive, retrieve information … and to stay alive. Testing these API’s (endpoints) is critical to ensure an application continues to function properly, provides the information an application needs and ensures there is no interruption of service.
But … testing is something that developers fundamentally avoid, ignore or overlook. Testing is boring, tedious and takes precious time away from the fun stuff, the work that needs done, the building of features or shiny new components that are important. Simplifying this effort, of testing and having those tests run automatically, with dynamic data parameters and optionally on a scheduled basis is where CodeNeighbor comes to the rescue.
This initial release provides the core foundation of defining an API endpoint, its’ required parameters and headers and the ability to save the result are now available in the version just released today – version 2.7. Work has started on improving this feature to provide data driven tests, using data created in the data artifacts widget, that can provide varied testing situations, simulating real world scenarios and reviewing the results ensuring success or failure.
Additionally, having these tests run on a scheduled basis will also be possible by enabling a feature typically only available to higher subscription levels and that being by using the CRON scheduler. The CRON widget itself will not be available (in full feature mode) to free or entry level subscribers in full, but only allowing scheduling of API test harnesses with somewhat limited scheduling capabilities. If your subscription level allows for full CRON capabilities, stay tuned for advanced features integrating CRON with API testing … in the mean time – happy testing !