Simplified the reporter API and added support for third-party reporters #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I removed the need for reporters to inherit from
Base
and moved all of the static methods that were part ofBase
into theutils
module. TheRunner
now collects the common stats (# of suites, # of benches and elapsed time) and passes the stats to the reporter as the argument to theend
event listeners. Each reporter now is simply a module that exports a function of the following form:Lastly, I added support for using third-party reporters. Third-party reporters can either be installed via
npm
in the user's project or they can be referenced using a relative path that is considered relative toprocess.cwd()
. For example:Thanks for creating this module! I found it very helpful when building templating benchmarks: https://github.com/raptorjs3/templating-benchmarks
I wanted to be able to easily report additional information--hence the need for this Pull Request.
--Patrick