Skip to content

Script (project)

One of the main resource types on the Skybear.NET platform is the Script project. In our docs we often just use the term Script, omitting the “project” word.

The Skybear.NET Script is a collection of Hurl source files.

Like in a movie the script describes the whole story, across many scenes, involving many actors, a Skybear.NET Script defines the whole sequence of requests and assertions to do in your workflow across many files.

Even though the dashboard UI editor only allows you to edit a single Hurl source file, when using the API to trigger a script run you can actually provide as many Hurl source files as you wish (see HTTP Hook trigger docs). We plan to expand the UI editor to support multi-file editing.

A Script is uniquely identified by an ID prefixed with s_.

Example

A single Hurl source file can be the following:

file-1.hurl
GET https://www.skybear.net/_live-demo/secure.json
HTTP 403
GET https://www.skybear.net/_live-demo/secure.json
Authentication: Bearer sample-token-123
HTTP 200
[Asserts]
body == "{\"ok\":true}"

And this is another one:

file-2.hurl
GET https://www.skybear.net/_live-demo/get.json
HTTP 200
[Asserts]
# Roundtrip should be less than 1 second.
duration < 1000

These are 2 Hurl source files, and can be part of a single Skybear.NET Script (project).