somekittens / baddsert Goto Github PK

• Travis Badge
• npm badge/poster
• greenkeeper

Docs

• Mocha injection
• Better CLI examples
• .baddrc (when that's a thing)
• whatever else I think of

.baddrc or somesuch. Users should be able to customize:

• badd baseline folder
• log level.

Using .only in mocha results in files being written that are only concerned with the one running test. We shouldn't delete things when they don't show up.

Right now I'm just using console.log all over the place.

Yeah, so I should probably compile this down to something more compatible.

A good chunk of the time, we know what value we want the test to be (at least initially).

The big problem is that if the code's wrong the first time (mreh) then the baseline will be wrong. Come up with some way to say "This is a first run, check everything new" (heck, should that be a default?)

Probably something in the lib we're using to interface with the user ignoring all other keypresses. Still, this is a bug.

instead of

let someStupidName = baddsert('blalalal');

Just figure out the name of the file calling us and use that. It'll be easier when there's a 1:1 mapping of file names.

This way it's easier to scan and distinguish between the message from baddsert and the actual values being discussed.

Chai has some sweet diff logging functions that would be neat to have when comparing baseline and recent.

https://www.npmjs.com/package/js-beautify

baddsert('tag', someVal, (old) => someVal === old);

Can't save them, due to the whole 'unique' thing.

¯_(ツ)_/¯

https://github.com/tj/better-assert

Have the CLI call npm test and then run the checks so it's all in one command.

• baddsert.throws

Having difficulty figuring out where things like greaterThan and within fit into BADD.

JSON has trouble with functions, dates, undefined, etc. Find a decent lib and use that instead.