Comparing version 0.2.1 to 0.2.2
@@ -22,3 +22,3 @@ 'use strict'; | ||
let depth = 0; | ||
let greenCheck = colors.green('✓'); | ||
let greenCheckmark = colors.green('✓'); | ||
@@ -48,3 +48,3 @@ let check = (resultSet, subKey) => { | ||
if (!resultSet.hasOwnProperty('current')) { | ||
leftLog(depth, `${greenCheck} ${subKey}`); | ||
leftLog(depth, `${greenCheckmark} ${subKey}`); | ||
depth--; | ||
@@ -60,3 +60,3 @@ return; | ||
leftLog(depth, `${greenCheck} ${subKey}`); | ||
leftLog(depth, `${greenCheckmark} ${subKey}`); | ||
} catch (e) { | ||
@@ -63,0 +63,0 @@ leftLog(depth, colors.red(`X ${subKey}: AGH THEY DON'T MATCH ${colors.trap('DOOOOOOOM')}`)); |
@@ -22,3 +22,3 @@ 'use strict'; | ||
var depth = 0; | ||
var greenCheck = colors.green('✓'); | ||
var greenCheckmark = colors.green('✓'); | ||
var check = function (resultSet, subKey) { | ||
@@ -46,3 +46,3 @@ depth++; | ||
if (!resultSet.hasOwnProperty('current')) { | ||
leftLog(depth, greenCheck + " " + subKey); | ||
leftLog(depth, greenCheckmark + " " + subKey); | ||
depth--; | ||
@@ -55,3 +55,3 @@ return; | ||
assert_1.deepStrictEqual(resultSet.reference, resultSet.current); | ||
leftLog(depth, greenCheck + " " + subKey); | ||
leftLog(depth, greenCheckmark + " " + subKey); | ||
} | ||
@@ -58,0 +58,0 @@ catch (e) { |
{ | ||
"name": "baddsert", | ||
"version": "0.2.1", | ||
"version": "0.2.2", | ||
"description": "Baseline Acceptance Driven Development for JavaScript", | ||
@@ -5,0 +5,0 @@ "main": "dist/index.js", |
@@ -9,5 +9,5 @@ # baddsert | ||
General idea: It's annoying to maintain tests. Every time you change an api, all the tests fail and they need to be manually updated. | ||
It's annoying to maintain tests. Every time you change an api, all the tests fail and they need to be manually updated. | ||
BADD keeps tracks of the new info on failures and allows you to automagically update the expected data. | ||
`baddsert` allows you to keep the data of tests separate from the test themselves, allowing you to update each separately for cleaner diffs and sane programmers. `baddsert` keeps tracks of the newly-provided data on failures and provides a CLI to update the expected data. | ||
@@ -66,3 +66,3 @@ ### Use | ||
When installing as a dev dependency it is recommended you add this to your npm scripts in your package.json | ||
When installing as a dev dependency I recommend you add a npm script to your package.json: | ||
@@ -77,6 +77,6 @@ ```json | ||
Then you can run baddsert as such (without requiring a global install) | ||
Then you can run baddsert without requiring a global install | ||
```sh | ||
$ npm run baddsert | ||
$ npm run baddsert -s | ||
``` | ||
@@ -83,0 +83,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
39263