
Security News
CVE Volume Surges Past 48,000 in 2025 as WordPress Plugin Ecosystem Drives Growth
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.
rescript-test
Advanced tools
A lightweight test framework for ReScript
Check out the documentation!
Run the following in your console:
$ yarn add --dev rescript-test
Then add rescript-test to your bsconfig.json's bs-dev-dependencies:
{
"bs-dev-dependencies": [
+ "rescript-test",
]
}
$ # All tests
$ retest 'test/**/*.bs.js'
$ # Single file
$ retest 'test/MyTest.bs.js'
The test framework can simulate a browser using JSDOM, to activate it, simply add the --with-dom option.
$ # All tests
$ retest --with-dom 'test/**/*.bs.js'
$ # Single file
$ retest --with-dom 'test/MyTest.bs.js'
open Test
let intEqual = (~message=?, a: int, b: int) =>
assertion(~message?, ~operator="intEqual", (a, b) => a === b, a, b)
let stringEqual = (~message=?, a: string, b: string) =>
assertion(~message?, ~operator="stringEqual", (a, b) => a == b, a, b)
test("Equals", () => {
let a = 1
let b = 1
intEqual(a, b)
})
let isCharCode = (a, b) => {
a->String.charCodeAt(0) === b
}
test("Custom comparator", () => {
let a = "a"
assertion(~message="Char code should match", ~operator="isCharCode", isCharCode, a, 97.0)
assertion(~message="Char code should match", ~operator="isCharCode", isCharCode, a, 98.0)
})
type user = {username: string, id: string}
let userEq = (a, b) => a.id === b.id
let userEqual = (~message=?, a: user, b: user) =>
assertion(~message?, ~operator="userEqual", userEq, a, b)
test("DeepEquals", () => {
let a = {username: "user", id: "a"}
let b = {username: "user", id: "a"}
stringEqual(a.username, b.username)
userEqual(a, b)
})
Outputs:
1/4: Equals
PASS - No message
2/4: Custom comparator
PASS - Char code should match
FAIL - Char code should match
---
operator: isCharCode
left: a
right: 98
...
3/4: DeepEquals
PASS - No message
PASS - No message
4/4: Async
PASS - No message
# Ran 4 tests (6 assertions)
# 3 passed
# 1 failed
test(name, body)createTestWith(~setup: unit => 'a, ~teardown: 'a => unit=? -> testtestAsync(name, body)createTestAsyncWith(~setup: unit => 'a, ~teardown: 'a => unit=?, name, body: ('a, cb) => unit) -> testAsyncthrows(func, ~message: string=?, ~test: exn => bool=?)doesNotThrow(func, ~message: string=?)assertion(comparator, a, b, ~operator: string=?, ~message: string=?)pass()fail()todo(string)let stringMapEqual = (~message=?, a, b) =>
assertion(
~message?,
~operator="stringMapEqual",
(a, b) => Belt.Map.String.eq(a, b, (a, b) => a === b),
a,
b,
)
Those that be useful to transition from an existing testing library, but we do not recommend polymorphic checks.
let equal = (~message=?, a, b) => assertion(~message?, ~operator="equal", (a, b) => a === b, a, b)
let deepEqual = (~message=?, a, b) =>
assertion(~message?, ~operator="deepEqual", (a, b) => a == b, a, b)
The setup function returns a clean context for the test, the teardown function resets it.
let testWithRef = createTestWith(~setup=() => ref(0), ~teardown=someRef => someRef := 0)
testWithRef("Setup & teardown", someRef => {
incr(someRef)
equal(someRef.contents, 1)
})
If you want to test with React, you can add the following helper as your test utility file:
@bs.val external window: {..} = "window"
@bs.send external remove: Dom.element => unit = "remove"
let createContainer = () => {
let containerElement: Dom.element = window["document"]["createElement"]("div")
let _ = window["document"]["body"]["appendChild"](containerElement)
containerElement
}
let cleanupContainer = container => {
ReactDOM.unmountComponentAtNode(container)
remove(container)
}
let testWithReact = createTestWith(~setup=createContainer, ~teardown=cleanupContainer)
let testAsyncWithReact = createTestAsyncWith(~setup=createContainer, ~teardown=cleanupContainer)
And then use it:
testWithReact("Can render", container => {
act(() =>
ReactDOMRe.render(
<div> {"hello"->React.string} </div>,
container,
)
)
let div = container->DOM.findBySelectorAndTextContent("div", "hello")
isTrue(div->Option.isSome)
})
testAsync("My test", (cb) => (
// your tests
cb(~planned=2, ())
))
Add a retest.env.js to your project root directory for any setup.
FAQs
> A lightweight test framework for ReScript
The npm package rescript-test receives a total of 424 weekly downloads. As such, rescript-test popularity was classified as not popular.
We found that rescript-test demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.

Security News
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.

Security News
Tailwind Labs laid off 75% of its engineering team after revenue dropped 80%, as LLMs redirect traffic away from documentation where developers discover paid products.