Skip to content
↑↓ move↵ openesc close

Reference

Known limitations

What Luvin does not do yet.

1 min read

These are the things Luvin does not do yet. Check them before you plan a test, so a missing feature does not surprise you.

  • Messaging steps are simulated. Luvin does not connect to Kafka, AMQP or MQTT yet; the app says so before running.
  • CORS (browser version only). The API under test has to allow the app’s origin (see connection help). Browsers cannot send cookies or the Host header. The desktop app has none of these restrictions.
  • Unsigned desktop installers, tested on macOS. Windows and Linux builds have not been tried on those systems yet.
  • gRPC and NTLM only in the desktop app. gRPC needs the .proto (no server reflection yet) and client-streaming and bidirectional methods send a single message.
  • No custom WebSocket headers, in the browser or in the desktop app (both open the connection like a browser). Pass a token in the URL instead, for example ?token={{token}}.
  • Workflow steps send payload fields, not files. A step with a multipart/form-data body is sent as multipart: each payload field is a part, a list gives one part per item, and an object is sent as JSON. A step cannot attach a file. Single requests do support files and binary bodies: see Send a file.
  • Swagger UI for OpenAPI only. AsyncAPI contracts use Luvin’s own preview.
  • XPath 1.0. Functions specific to XPath 2.0 or 3.0 are not available.
  • No hosted version yet. Run it locally, use the desktop app or serve the static build.