This repository has been archived by the owner on Dec 20, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 36
Support full JS in test scripts #101
Comments
@tpluscode |
I honestly don't have the faintest clue about it 😅 |
@tpluscode |
Here's another example. In my test I wrote client.test("Created sortBy:title properties", function() {
const {bindings} = JSON.parse(response.body).results
const total = bindings[0].total.value
client.assert(total == 0, `${total} records found without sort title`);
}); But it also fails with the |
@tpluscode |
Great feature request. |
Hello, any progress on this project, or is it already dead? does anybody know another alternative to run the Jetbrains http request files from commandline with support for the latest features and no bugs? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Without being able to reuse existing JS packages and reuse test scripts, the tests will quickly become very repetitive. I would like to write a test using anything node has at its disposal.
The
test-helper.js
script could be something likeThis way would be possible to write more concise and idiomatic tests
Currently, when I tried
import
orrequire
the script does not even parse and throws an errorHere's a GraalVM example, which might be helpful. Rather than a simple
eval
, a context is created which should allow importing scripts and package. The latter is not show as example but implied on the linked pageThe text was updated successfully, but these errors were encountered: