intern
intern copied to clipboard
theintern
A next-generation code testing stack for JavaScript.
Since upgrading from Intern 3 to Intern 4 we have a number of files that have (much) lower code coverage. I've been able to chase this down to test cases...
In the past, browsers had non-zero default values for the functional timeouts (page load, find, and async exec). Today (and for a little while), this hasn't been the case, and...
GitHub Actions virtual environments (linux and windows) expose a `CHROMEWEBDRIVER` environment variable that points to the local chromedriver.exe. Intern should be able to use this information to allow use of...
See https://github.com/theintern/intern/issues/314 Intern currently uses Selenium to manage browsers, which requires Java. The Java requirement is becoming more of a burden as time goes on, and most browsers have native...
The paths to the loaders (Dojo, SystemJS, ...) are hardcoded in the loader scripts in Intern 4. Consider making them configurable with a loader option.
Add documentation for the tunnel classes. Current documentation is in the Dig Dug repo.
Add documentation for Intern's webdriver API. Existing documentation is in the Leadfoot repo.
Intern 4.x and 5-pre use Sauce Connect's Selenium Relay when running tests on Sauce. Sauce Connect is setup to listen on the standard Selenium port 4444 with the `-P` option,...
The Console reporter used when running browser tests doesn't currently (as of Intern 4.8.x / 5.0.0-pre) output debug log statements when `debug` is active. It should.
As mentioned in #1020, Intern should provide some level of file watching services. This would allow Intern to detect changes to tests, and optionally application files, and automatically re-run tests....