1. Overview
  2. Docs
Melange bindings for testing-library (dom-testing-library and react-testing-library)

Install

dune-project
 Dependency

Authors

Maintainers

Sources

melange-testing-library-0.2.0.tbz
sha256=20192de29aeef985630e79b18f232dd58cb524eabe4894b163dd0b62b57d594d
sha512=1126fdc8fa9b6ddba43d070ffa3ae124b833fb1dfd1cbd3d63c06bf167a07dfe8c7f5de9db68bc8589ab17e27a220feb49c2f95390cd292630e640aa1d0d38f0

Description

Added to opam-repository:

README

melange-testing-library

Melange bindings for testing-library (dom-testing-library and react-testing-library)

Install

Install opam package manager.

Then:

opam install melange-testing-library

The bindings support the following versions of the @testing-library/react and @testing-library/dom npm packages, which should be installed separately:

  "devDependencies": {
    "@testing-library/react": "^11.1.0",
    "@testing-library/dom": "^7.26.3",
  }

Setup

Add melange-testing-library.dom and melange-testing-library.react to the libraries in your dune file:

; ...
  (libraries melange-testing-library.dom melange-testing-library.react)
; ...

Dependencies (4)

  1. reason-react
  2. melange >= "5.0.0"
  3. ocaml
  4. dune >= "3.8"

Dev Dependencies (5)

  1. odoc with-doc
  2. bisect_ppx with-test & >= "2.5.0"
  3. melange-webapi with-test
  4. opam-check-npm-deps with-test
  5. melange-jest with-test

Optional Dependencies

None

Conflicts

None

Build status

Results of building melange-testing-library with each compiler on check.ci.ocaml.org, run of against opam-repository 78c202b. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
0.2.0 (this version) n/a good good good good
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure