Tree: 8f80ed104c

babel-plugin-for-integration-tests

browser-recipe

browser-support

export-module

failure-output

faster-string-diff

fix-readme-improvements

fix-string-diff-colours

hoisting-throws-helper

master

refactor-reporters

replace-snapshot

safe-default-concurrency

upgrade-xo

use-hullabaloo

v0.1.0

v0.10.0

v0.11.0

v0.12.0

v0.13.0

v0.14.0

v0.15.0

v0.15.1

v0.15.2

v0.16.0

v0.17.0

v0.18.0

v0.18.1

v0.18.2

v0.2.0

v0.3.0

v0.4.0

v0.4.1

v0.4.2

v0.5.0

v0.6.0

v0.6.1

v0.7.0

v0.8.0

v0.9.0

v0.9.1

v0.9.2

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '8f80ed104c'

${ noResults }

Commit Graph

445 Commits (8f80ed104c2c72dfa8ad9e98f2455cf36f09b72d)

Author	SHA1	Message	Date
James Talmage	0276c63bd0	Move method chaining to an external module (`option-chain`)	9 years ago
James Talmage	93097ea7ba	bump observable-to-promise Observable `0.2.0`/`0.3.0` introduced some breaking changes. Namely, it now throws if passed a non-observable. Reference: https://github.com/sindresorhus/observable-to-promise/issues/2	9 years ago
James Talmage	e7bdd7de71	Add babel-runtime and core-js to list of internals. Fixes #429	9 years ago
James Talmage	af37305e35	use stack-utils for nicer stack traces.	9 years ago
James Talmage	3d7f036a39	Prevent log corruption when using mini reporter. Fixes #392. This prevents interference between the mini logger and child processes that use `console.log`. The mini reporter previously used logUpdate which deletes lines previously written with the logUpdate API before writing a new one. This caused problems if lines from console.log were written inbetween logUpdate calls. It would delete the users log messages instead of the test status line. To fix this, we store the last written last log line, clear it, write the users log output, then restore the last log line. This keeps the miniReporter output always at the bottom of the log output. It also fixes an incorrect use of the `child_process` API. We were using the `stdio` option for `child_process.fork`, but that option is ignored (it is honored for just about every other method in that API). See: 7b355c5bb3/lib/child_process.js (L49-L50) It also adds a set of visual tests which can be run via `npm run visual`. They must be run manually, and should be run as part of our pre-release process.	9 years ago
Kevin Lanni	eea8752a79	Close #414 PR: Fix t.throws/doesNotThrow not outputting failure reason.	9 years ago
Takuto Wada	70dd2a7e5f	update empower-core and babel-plugin-espower to make `t._capt` and `t._expr` unnecessary - babel-plugin-espower 2.1.0 embeds value capturing helper (`_capt` and `_expr`) into transpiled code. Therefore, copying `t._capt` and `t._expr` is not required any more - In addition, babel-plugin-espower 2.1.0 is refactored a lot to reduce dependencies - empower-core 0.4.0 stop adding `_capt` and `_expr` methods into assertion object refs: https://github.com/sindresorhus/ava/pull/302#issuecomment-161933270 refs: https://github.com/power-assert-js/babel-plugin-espower/pull/11 refs: https://github.com/twada/empower-core/pull/3	9 years ago
James Talmage	7b764ea3be	Close #412 PR: Standardize colors across reporters.. Fixes #410	9 years ago
Juan Soto	a2b282eba2	Close #410 PR. Print skip count in yellow for all reporters. Fixes #408	9 years ago
James Talmage	614eb121ff	Transpile test files in the main process: Squashed commits: transpile in the main thread drop unused dependencies incorporate PR feedback add tests add unit tests	9 years ago
James Talmage	821436aec6	Regression: Assertions should return promises. This fixes that regression, and extends the promise returning behavior to all assertions. This would be useful in `async` test functions to bail on the remaining tests if some precondition fails. Simply `await` the assertion.	9 years ago
James Talmage	da6a2f4ab0	use long stack traces in forks.	9 years ago
vdemedes	bef1dfb864	support promises rejected with non-Errors	9 years ago
James Talmage	6033e9c2e0	Hide annoying error print outs. Fixes #339	9 years ago
vdemedes	e30685f233	display power-assert output in mini reporter	9 years ago
Ari Porad	0729997882	Rename lib/babel.js to lib/test-worker.js	9 years ago
vdemedes	ac468d1fa8	use AvaError for internal errors	9 years ago
Ari Porad	e52db69261	Close #360 PR: Fix promise assertions. Fixes #309	9 years ago
Sindre Sorhus	4865674403	minor cleanup	9 years ago
Sindre Sorhus	0a40bdb119	use relative file paths on the fork.js output	9 years ago
vdemedes	cbea003517	show full stack trace for non-assert errors	9 years ago
vdemedes	2c77314f93	add mini reporter	9 years ago
vdemedes	0daec3e2e1	cache babel-transpiled code	9 years ago
vdemedes	2fab4b1e53	introduce reporters	9 years ago
Ari Porad	ae446f0741	Make --require relative to where the command is run closes #346	9 years ago
James Talmage	94797b1038	Require babel plugins directly. Fixes #350. Also seems to make Babel 5 support "just work".	9 years ago
James Talmage	9e6d9724d5	Close #333 PR: Upgrade to Babel 6.	9 years ago
vdemedes	a5e63c0d43	add TAP support	9 years ago
Sindre Sorhus	a6e21e2933	remove undocumented `t.assert` assertion It was just an alias for `t.ok` and pretty sure I was the only one using it.	9 years ago
James Talmage	072ab8576f	Close #330 PR: use `empower-core` for better assertion tracking and performance.	9 years ago
Juan Soto	ad7ae194ef	Close #325 PR: Stop hiding source of syntax errors. Fixes #308	9 years ago
Sindre Sorhus	d0c370a1c0	don't use local Babel directly Instead depend on npm to dedupe. This is better as we will no longer fail if the user has Babel 6 and we Babel 5, and npm just won't dedupe. Same situation in the future when we're on Babel 6, but the user is still on Babel 5.	9 years ago
Juan Soto	da3c7a8359	Add default message to x.fail(), update related test	9 years ago
Ron Waldon	6081389d00	Node.js-style --require CLI argument	9 years ago
Ron Waldon	eeeec706c2	process is forked with a single JSON argument	9 years ago
Mark Wubben	be8b935130	source-map-support@0.4.0 Now automatically retrieves the source map from the file itself.	9 years ago
Sindre Sorhus	ff5b8dfa5c	switch to `resolve-cwd` dep	9 years ago
James McMath	8a6770423d	Close #303 PR: Adds filename to failed test title.. Fixes #272	9 years ago
James Talmage	e0f31e8409	allow destructuring of `t` parameter. There were two problems with using destructuring on the `t` parameter passed to tests: 1. `t.end` is enumerable, but throws when accessed. This created problems when destructuring using rest params `{ok, ...t}`. The solution: `t.end` is enumerable only in "callback mode". 2. `t._capt`, `t._expr` are not enumerable, and therefore not exposed as a member of the `...t` rest param. The only solution was to make them enumerable. Not ideal, but better than the confusing error that previously occurred.	9 years ago
James Talmage	357622c283	Add ability to skip individual assertions. Fixes #9.	9 years ago
vdemedes	cf471cb1ee	display skipped tests	9 years ago
James Talmage	56cd65265e	Allow deepEqual comparison of values with circular references. Fixes #298. Introduces an additional dependency: `deeper`. Fixes #298. Alternate to #300.	9 years ago
James Talmage	3f2e67a45b	Forward all child output to `stderr` on main process. Closes #291 Closes #291	9 years ago
James Talmage	eef3d8832a	Unify how files with no tests are reported. There are two possible errors that can result in no test data being received. 1. The user never imports `ava` in their test file. 2. The user has not written any tests in the file yet. We treat both as errors, but were handling them differently. Most problematic, one caused the promise to resolve, the other caused the promise to reject.	9 years ago
James Talmage	c78c46fa85	Hide test internals. Fixes #252. Fixes #252.	9 years ago
vdemedes	c424ceb3d3	Close #279 PR: Add programmatic API. Fixes #83	9 years ago
James Talmage	717030813a	test.async -> test.cb	9 years ago
James Talmage	5e927454d3	Integrate time-require when `debug` is enabled. I want to start focusing on getting our require times down, both in the main thread and forked tests. This adds `time-require` support directly to the CLI to assist in that. This is especially important for forked test processes, where I currently have to manually add a line of code each time I want to test an optimization. I don't think this should be a publicly documented move. I think we want the freedom to remove this once we are happy with performance. I have placed comments above all `time-require` references, indicating it is for internal use only. Users have been given fair warning against relying on its inclusion long term. Usage: ```sh $ DEBUG=ava ./cli.js test/fixture/es2015.js --sorted ``` `--sorted` is optional. It sorts the requires from most expensive to least. The default is sequential sorting. The output will display multiple `time-require` reports. One for each forked process, and the last one for the main thread.	9 years ago
James Talmage	f8168153c7	Breaking: t.plan() will not auto-end tests. AVA will no longer automatically end tests when you reach the plan limit. Users must explicitly call t.end(). It is now an error to return an async object (promise/observable) from a legacy `test.async` test. Reference: https://github.com/sindresorhus/ava/issues/244#issuecomment-159348943	9 years ago
James Talmage	0ef0ca14fc	Pipe forked IO streams instead of forwarding `data` events. This passes terminal width information to, and enables ansi-color support in, the forked process. It makes the output of `time-require` much prettier when used in a fork.	9 years ago