tests: improve names of tests; separate methods passesWith / failsWith (implementations are going to be different)
tests: "customEqualsTwo" -> "customEqualsTwo" (name and semantics), + testing it with actual string value "2"
tests: made explicit which are the arguments for the first ("partial") application of the assertion
tests: rewrote former "testPartial" as "makeTest", similar to tests of referee; better test names from buster.format. Left in old style for comparison
tests: removed old-style testPartial; inlined helper fn "testName"
new test: found a bug - combinators.assert.equals(42)("42") should behave like assert.equals(42, "42") (i.e. *pass*)
+ one more test, to be sure that it's not our tricky helper fn makeTests (it is in fact not)
fix: pass on optional message (TODO: test it)
tests: fix name - custom assertion "equalsTwo" is actually binary, not unary
tests: add some comments re jslint complaining
adjust test: equals was coercing in buster <= 0.6.12 but *is not anymore* in referee!
see https://github.com/busterjs/referee-combinators/pull/2#issuecomment-13371263
tests: workaround for making it run in dev-env; silence jslint; improved comments
temporarily having referee vs buster.assertions (buster 0.6.12) is even better - we might find more discrepancies
refactor tests: moved helper function `makeTests` to file test-helper.js
refactor tests
refactor tests: tried to move adding custom assertion into `setUp` but doesn't work. Why?
make test for custom assertion pass again
Merge branch 'develop' of https://github.com/busterjs/referee-combinators into integrate_attr

Conflicts:
	lib/referee-combinators.js
	test/referee-combinators-test.js
remove lints from test
add TODO: we should allow an optional message in *both* stages, preparing (when "expected" is specified) AND execution (when "actual" is specified) - with the latter, if present, overriding the former. However, this requires specialisation on the arity of the assertion.