Version-controlled API tests for VS Code and CI
Turn API requests into tests your whole team can keep — authored and debugged in VS Code, run on every PR in CI.
Define version-controlled API tests that combine requests, scripts, SQL checks, assertions, and environment-aware runs.
Import endpoints and schemas once, then reuse the same API definitions across every workflow.
swagger "https://petstore.swagger.io/v2/swagger.json"
endpoints
GetPetById: GET {{baseUrl}}/pet/{petId}
PlaceOrder: POST {{baseUrl}}/store/order
end endpointsCreate data, call services, run helpers, query databases, and carry values forward in one readable sequence.
sequence VerifyOrderFlow
run bash ./scripts/seed-db.sh
var data = run js ./scripts/sign.js {{payload}}
var row = run sql FindOrder(data.id)
end sequenceUse VS Code while building, then run the same workflow files from the CLI in CI.
norn tests/ --env prelive
norn tests/ --junit results/junit.xmlContracts, validations, and coverage stay connected in the same version-controlled tests.
Norn keeps API tests close to development. Use VS Code when you are shaping a flow, then run the same version-controlled files from the CLI when the tests become part of your release process.
Author the workflow beside your code with endpoints, environments, assertions, SQL checks, and helper scripts.
Create data, call services, capture response values, and pass them into the next step without switching tools.
Check status codes, payloads, schemas, timings, and database state so the workflow produces a clear signal.
Run the same .norn files from the CLI with environment selection, JUnit output, and HTML reports.
test sequence CheckoutWorkflow
run bash ./scripts/seed-cart.sh
POST {{baseUrl}}/orders
{
"cartId": "{{cartId}}"
}
assert $1.status == 201
var orderId = $1.body.id
run sql FindOrder(orderId)
assert $2.rows[0].status == "created"
end sequence
Keep request exploration, test automation, validation, database checks, and CI execution in the same developer-owned, version-controlled files.
Watch a quick walkthrough, then scan the example below to see how Norn turns API steps into version-controlled tests
Prefer a quick glance first? The example below shows the shape of a typical Norn workflow.
test sequence UserWorkflow # Create a new user POST {{baseUrl}}/users { "name": "Alice", "email": "alice@example.com" } assert $1.status == 201 var userId = $1.body.id # Verify the user was created GET {{baseUrl}}/users/{{userId}} assert $2.body.name == "Alice"end sequence$1.status == 201 $2.body.name == "Alice" Orchestration, validation, environments, and CI for API tests
Automate multi-step API workflows with response capture, variables, and references to previous steps using $1 and $2.
Turn every workflow into a release signal with equality, contains, regex, type, existence, schema, and timing checks.
Run the same automation against dev, staging, prelive, or production using .nornenv variables instead of editing requests.
Run workflow suites from local scripts and pipelines with JUnit and HTML reports for automated release gates.
Run and debug workflow sequences from VS Code's Testing sidebar with status codes, timings, and failure details.
Keep automated workflow coverage tied to Swagger/OpenAPI endpoints and expected response codes.
Organize API tests with purpose-built file types that keep flows, SQL, environments, and reusable definitions cleanly separated.
HTTP steps, sequences, assertions, and automation logic. This is where your workflows live.
Reusable headers, endpoints, and Swagger imports. Define once, use everywhere.
Named queries and commands that let workflows verify state in Postgres, SQL Server, or custom adapters.
Variables for dev, staging, prelive, and production. Switch contexts without changing workflows.
Norn can send API requests, but the product is aimed at version-controlled API testing: sequences, assertions, environments, SQL checks, and CLI execution.
Yes. You can build and debug workflows in VS Code, then run the same files with the Norn CLI in local scripts or CI.
Norn can import Swagger/OpenAPI definitions so endpoints, schemas, and coverage stay tied to the same contract your team already maintains.
Yes. Norn supports named SQL operations, with built-in Postgres and SQL Server support plus custom adapters when needed.
Workflows produce direct pass/fail signals through assertions and can emit JUnit and HTML reports, making them suitable for automated release gates.
Install Norn from the VS Code Marketplace or book a demo to see how it fits your API testing.