qunit-phantomjs-runner
Advanced tools
A PhantomJS-powered headless test runner, providing basic console output for QUnit tests.
The runner requires PhantomJS. If you don't want to deal with installing PhantomJS or using Grunt to run your tests, try node-qunit-phantomjs.
$ npm install qunit-phantomjs-runner
$ phantomjs path/to/runner.js [url-of-your-qunit-testsuite]
With options:
$ phantomjs [phantom arguments] path/to/runner.js [url-of-your-qunit-testsuite] [timeout-in-seconds] [page-properties]
Show test cases:
$ phantomjs path/to/runner-list.js [url-of-your-qunit-testsuite]
Example setting the viewport size:
$ phantomjs path/to/runner-list.js [url-of-your-qunit-testsuite] 5 '{"viewportSize":{"width":1000,"height":1000}}'
In v2.0, a default timeout of 5 seconds was added. The timeout was optional before. This could cause tests to break, which is the reason for the major version bump.
The MIT License
Copyright (c) 2014, Jonathan Kemp
FAQs
A PhantomJS-powered headless test runner for QUnit
We found that qunit-phantomjs-runner 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.