Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A programmatic interface for the test runner #823

Closed
nicojs opened this issue Oct 23, 2017 · 3 comments
Closed

A programmatic interface for the test runner #823

nicojs opened this issue Oct 23, 2017 · 3 comments
Labels
needs-opinions Needs opinions to decide how to handle needs-verification Needs to be verified

Comments

@nicojs
Copy link

nicojs commented Oct 23, 2017

We're looking into supporting intern in Stryker, the JavaScript mutation testing framework.

In order to support intern, we need a programmatic interface to interact with the test runner. Basically what we'll be doing is writing small changes (or mutants) to the input files. Each time we've mutated a file, we will start another test run and report the results. Our adapter interface looks like this: https://github.com/stryker-mutator/stryker/blob/master/packages/stryker-api/src/test_runner/TestRunner.ts

Is it be possible to programmatically interact with the test runner? If not, are there any plans to add it?

Original feature request here: stryker-mutator/stryker-js#430

@kitsonk
Copy link
Contributor

kitsonk commented Oct 23, 2017

References this discussion on gitter: https://gitter.im/theintern/intern?at=59edb682f7299e8f531f514c

@kitsonk kitsonk added needs-opinions Needs opinions to decide how to handle needs-verification Needs to be verified labels Oct 23, 2017
@jason0x43
Copy link
Member

Intern has a programmatic API that seems like it should work with your TestRunner adapter. We have a simple how to section in the docs on using the programmatic API. The included grunt task is another example of using this interface.

@jason0x43
Copy link
Member

Closing this since it should be resolved with the existing API. Feel free to re-open if that's not sufficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-opinions Needs opinions to decide how to handle needs-verification Needs to be verified
Projects
None yet
Development

No branches or pull requests

3 participants