Limiting tests executed during package build when generating opam files with dune

Is there a way to limit which tests get executed by default by dune? Especially in case when generating opam files.

Basically my use case is that, in letters, I have some tests that I would like to execute always, while some tests I would like to skip and expect to be executed manually. I don’t want CI to run some of the tests, because they need non-released version of a dependency and depend on an availability of an external service (I’m using ethereal.email to test that I can successfully send some emails).

I would prefer dune to generate opam files, but I don’t see a way to limit which tests gets executed when doing the release. Instead of having:

build: [
  ["dune" "subst"] {pinned}
  [
    "dune"
    "build"
    "-p"
    name
    "-j"
    jobs
    "@install"
    "@runtest" {with-test}
    "@doc" {with-doc}
  ]
]

I would like to have something like:

build: [
  ["dune" "subst"] {pinned}
  [
    "dune"
    "build"
    "-p"
    name
    "-j"
    jobs
    "@install"
    "@test/runtest" {with-test}
    "@doc" {with-doc}
  ]
]

The difference is with the to have @test/runtest instead of @runtest. I haven’t been able to find anything from the documentation that would allow me to change this part of the generated opam file.

Thanks.

6 posts - 4 participants

Read full topic