v0.777.77-beta — webpack 3 compatibility

• This makes test-bed compatible with webpack 3. (webpack 4 later)

v0.77.77 — Many new stuffs!!

This release brings a lot of cool stuffs from contributors. Thanks a lot for contributions, and sorry that I haven’t taken the time to maintain this project for several months.

• Now you can specify which webpack configuration file to use. (#6) Contributed by @lukastaegert
• You can use webpackMiddleware option to override webpack-dev-middleware configuration. (#9) Contributed by @meta-meta
• Reduced noise in webpack output by default (#10) Contributed by @lukastaegert
• Added CLI and configuration option to launch default browser when test-bed is run. (#10) Contributed by @lukastaegert
• Allowed changing port from configuration file in addition to from the CLI. (#10) Contributed by @lukastaegert
• Improved webpack 2 compatibility.
• Added end-to-end test for this project so we know things are still working.
• Set up Git-based deployment to npm via CircleCI, which makes it easier for me to release new versions. Also switched to my own weird versioning scheme which is compatible with semver.

v0.6.0 — Stack traces for Mocha adapter.

In this release, we upgraded the Mocha adapter to log test failures to the console.

In previous version, when there is a test failure, the report shown in the browser window does not contain original source file information (because it does not have access to the source map).

In this version, we also log test failures to the console. This allows you to use your devtools to look at the stack trace, which contains the source mapping.

Hope this release will make your test workflow more enjoyable :)

v0.4.0

• Fixed a memory leak bug that caused the server to crash after many runs.
• Better coverage reports.
  • Coverage reports are now cached per-test-file. This leads to a more accurate report when changing the test files.
  • Coverage reports are now generated in a separate process. This also makes the server crash less often.
• Simpler test entry configuration. No more TestBed global in your test entry file.
• Test framework adapters. As test-bed becomes more sophisticated, more integration with the test framework (e.g. Mocha) is required. Forcing users to update their test entry file every time a new version is released is no good. test-bed now ships with adapters for test frameworks (only Mocha for now).