Calmjs.dev

------------------

- Provide the ``-T`` or ``--test-only`` flag to the ``karma`` runtime to
allow toolchain execution be terminated after the tests are executed
regardless of outcome. This would generally allow the test to run
without forcing the toolchain to build the artifact. [
`11 <https://github.com/calmjs/calmjs.dev/issues/11>`_
]

------------------

- Configuration writers that write out karma configuration scripts that
import other Node.js modules that are present within the environment
that the karma binary reside in should no longer encounter a ``Error:
Cannot find module`` message. [
`10 <https://github.com/calmjs/calmjs.dev/issues/10>`_
]
- Permit the use of other karma_conf dict/mapping types in the spec. [
`9 <https://github.com/calmjs/calmjs.dev/issues/9>`_
]

------------------

- Allow the karma configuration writer to be specified in the spec, such
that it may be overridden by framework integration packages. [
`8 <https://github.com/calmjs/calmjs.dev/issues/8>`_
]

------------------

- Support the correct resolution of test child module registries, which
was introduced in ``calmjs-3.3.0``. [
`6 <https://github.com/calmjs/calmjs.dev/issues/6>`_
]
- Ensure that a missing karma binary is also correctly dealt with by the
same set of exception and flags. [
`7 <https://github.com/calmjs/calmjs.dev/issues/7>`_
]

------------------

- Ensure the exit code indicates failure if the artifact test entry
point references an import that cannot be resolved (failure to set up
the test must result in a failure). [
`3 <https://github.com/calmjs/calmjs.dev/issues/3>`_
]
- Make use of the corrected semantics provided by calmjs-3.1.0 for the
deferred export location verification, which also silences the
calmjs-4.0.0 deprecation warning. [
`5 <https://github.com/calmjs/calmjs.dev/issues/5>`_
]

------------------

- Migration to the calmjs-3.0.0 API.
- Bumped a number of dependencies on Node.js packages.
- The paths that are covered by the test coverage report are now
recorded in the Spec as part of the test execution workflow through
the KarmaDriver.
- Provide framework and command for testing of predefined artifacts
generated for packages defined through the ``calmjs.artifacts``
registry; ``calmjs.artifacts.tests`` registry was created such that
toolchain packages may declare the test compliment builder functions
to facilitate testing for their dependent packages.
- Implemented ``--cover-report-type`` flag to support the specification
of multiple coverage report types to be generated, and ensured that
the defined report types actually work (a karma/istanbul bug was
found and a workaround was implemented).
- A number of internal code refactor, i.e. a number of internal API
changes have happened.
- Deprecated ``--coverage-type`` flag, as it is inconsistently named and
that features provided by ``--cover-report-type`` superseded this.
- Deprecated ``--test-package`` flag in favor of ``--test-with-package``
for more clarity about the intention of that flag.