Visualize how inputs flow through your modules with a step-by-step execution log of everything that happened. Watch a live view of your data with highlights of what changed to quickly detect, identify, and resolve configuration issues. Get insight into the inner workings of your modules, including a real-time preview by role.
Compare changes before approving release to the next environment. Mark, leave notes, or flag the most important versions. Search by tag or note, view promoted or starred versions, and revert to any previous version. Copy modules and make changes into a new module. View deltas between selected versions since the beginning of time.
The Service Logs Dashboard is a debugging tool that simplifies the visibility and searchability of API logs within Unqork. By reviewing, saving, and even sharing service logs in the Service Logs Dashboard, Creators can build & debug applications faster than they could when using a traditional code-based development approach.
The Signal Start node allows Creators to perform test runs of their workflows. Using these test workflows, Creators can review and experiment with application behaviors and automate testing activities such as initiating a QA ticket or interacting with an external testing framework.
With Unqork’s Test Harnesses, Creators can test & debug if/then logic within their application to ensure their application is properly configured and their business rules are functioning as expected.
Configure in development, test in UAT, and promote to production environments, with different users and permissions supported across each environment.
Test, in real time, the logic of input and outputs in calculated fields during the application’s build. Add inputs and immediately see outputs.
Build and run automated tests that can be run before and after release to maintain predictable execution of all applications.
Leverage “Application Promotion” endpoints to kick-off automated static or dynamic scans and conduct regular penetration testing of applications.
In the following article we break down how and why Unqork-built applications are decidedly less buggy than those built using a traditional code-based approach.
