@matvp91/webrun
Advanced tools
`webrun`'s goal is to provide a _lightweight_ CLI tool that runs your integration tests effectively in a local environment. While there's many alternatives out there, its main focus is on testing the integration of a library you've built in order to ensur
webrun's goal is to provide a lightweight CLI tool that runs your integration tests effectively in a local environment. While there's many alternatives out there, its main focus is on testing the integration of a library you've built in order to ensure that you ship a working module.
webdriver protocol and a strict API to provide interop between your local, remotely controlled browser and the test file.npm install @matvp91/webrun
Create the following structure in your project:
- /integration-tests // We'll use this folder name to write the test files.
- /public // Will be served by a local webserver.
- index.html
- basic.test.js // Your test file.
// basic.test.js
module.exports = {
name: 'A basic integration test',
run: async (/* typeof Browser */ browser) => {
await browser.runFunction(() => {
bootstrapMyModule();
});
// Example of an interop between the browser and the test scenario.
const result = await browser.runFunction(() => window.I_GOT_CALLED);
expect(result).toBe(true);
},
};
<!-- public/index.html -->
<html>
<body>
<script>
function bootstrapMyModule() {
// Gets called by the test runner through browser.runFunction(...).
// For the sake of this example, we'll assign a variable to window and
// retrieve it in our test runner.
window.I_GOT_CALLED = true;
}
</script>
</body>
</html>
// package.json
// In order to run the scenario, "npm run test:integration"
{
"scripts": {
"test:integration": "webrun integration-tests"
}
}
FAQs
`webrun`'s goal is to provide a _lightweight_ CLI tool that runs your integration tests effectively in a local environment. While there's many alternatives out there, its main focus is on testing the integration of a library you've built in order to ensur
The npm package @matvp91/webrun receives a total of 3 weekly downloads. As such, @matvp91/webrun popularity was classified as not popular.
We found that @matvp91/webrun demonstrated a not healthy version release cadence and project activity because the last version was released 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
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.
Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.