Skip to content
↑↓ move↵ openesc close

Reference

Frequently asked questions

Short answers to the questions testers and product people ask most, each with a link to the page that explains it in full.

5 min read

Short answers, each with a link to the page that goes deeper.

Luvin tests a chain of API calls, called a workflow, where each call uses data from the earlier ones. You design the workflow from your contracts, run it and read a verdict in plain words. It is not an automation or orchestration tool. See What is Luvin.

No. Luvin has no backend and no account. You open it and work. See Privacy and security.

No. Everything runs on your computer, in the browser or in the desktop app. The only traffic is the requests you run against your own APIs, and the contracts you choose to download from a URL. See Privacy and security.

Arazzo is an open standard of the OpenAPI Initiative for describing a sequence of API calls in a file. Luvin writes it for you when you design a workflow, and reads it when you open one. See The Arazzo file view and the Glossary.

Which versions of the specifications does it support?

Section titled “Which versions of the specifications does it support?”

Arazzo 1.0 and 1.1, OpenAPI 3.x, and AsyncAPI 2.x and 3.x. See Specification support.

Yes. The interface, the messages and the HTML report are in English and Spanish. Change the language in Preferences. See A tour of the interface.

Yes. Drag saved requests onto the canvas instead of contract operations. You can create requests from scratch, import a cURL command, or import a Postman or Bruno collection. See Build from saved requests and Bring your own files and requests.

No. You design on the canvas and Luvin writes the Arazzo file. See Design a workflow.

Yes. The YAML tab is the same file the canvas edits. What you write by hand is kept, and the tab validates it as you type. See The YAML tab.

In the workspace folder you choose: a folder with one subfolder for each collection, all plain files. Without a workspace, the session is saved on this device. See What is on disk and Use Luvin without a workspace.

Yes. A workspace is a folder of plain files and secret values are not in them, so you can commit it. See Keep a workspace in git.

What is the difference between Real API and Simulation?

Section titled “What is the difference between Real API and Simulation?”

Real API sends the requests to the URLs of the active environment. Simulation answers from the examples in the contract, with no network and no credentials. See Simulation.

Why does the run pause with a dialog about a list?

Section titled “Why does the run pause with a dialog about a list?”

A step returned a list and a later step uses it, so Luvin asks which item to continue with. Against the Real API it asks even when the list has one item. In Simulation it asks only when the list has more than one. See Choose an item from a list.

A Warning case is a data validation case where the API answered a status other than the one Luvin suggested, usually by accepting data the contract says it should reject. The workflow still works. See Why a step or a case failed.

Luvin could not judge it: the API did not answer, or the workflow stopped before the step the case checks. Fix the earlier problem and run again. See Read the results.

Why did a step fail when the API answered 200?

Section titled “Why did a step fail when the API answered 200?”

A success criterion of the step was not met, for example a field with another value. Open the step: the reason says what was expected and what arrived. With no criteria, any 2xx passes.

Why is the API not answering in the browser?

Section titled “Why is the API not answering in the browser?”

In the browser the API under test must allow CORS from the app’s origin. Luvin shows the exact headers to add. The desktop app has no CORS restriction. See Connection help.

It can. Steps with POST, PUT, PATCH or DELETE send real requests to the environment, and Luvin asks you to confirm before it runs them. Choose a test environment or use Simulation. See Run.

Press Report in the header of the results to get a self-contained HTML report without credentials, or JSON to export the results. See Reports.

Only the names of secrets are written in the workspace files. The values are encrypted on your computer, with the system keychain in the desktop app. See Base URLs, variables and secrets.

Yes. Set it per API or per workflow without changing the Arazzo; the token is fetched once and reused. See OAuth 2.0.

Not yet. AsyncAPI steps work, but they are always simulated from the contract examples, also in a real run. See Messaging steps and Known limitations.

Luvin is a tool to design, debug and show workflows. It is not a CI runner. The Arazzo files it writes can be taken to a tool that runs Arazzo in CI, such as Redocly Respect. See Known limitations.

Should I use the desktop app or the browser?

Section titled “Should I use the desktop app or the browser?”

Use the desktop app if you need cookies, no CORS limits, real folders, the system keychain, gRPC or a terminal. The browser works for a quick try. See Install and open Luvin.

How do I generate random data, such as a new email each run?

Section titled “How do I generate random data, such as a new email each run?”

Write a template such as {{email}} or {{$randomUUID}} in a value. See Dynamic variables and Runtime expressions.