power-assert-js / power-assert Goto Github PK

It seems like there is a great infrastructure around power-assert. More than this you provide a way for other assertion libraries to empowerment which is awesome! Nevertheless it seems like most of the instrumentors are power-assert-centric a bit (not a big surprise though =)). What I mean by that is implicit rewriting of require('assert') with hardcoded require('power-assert'). Would it be possible for all of these great instruments to provide an option to overwrite default power-assert with any other empowered assertion library? Alternatives that I see for such libraries either to ask their users to explicitly require them or maybe to recreate some of the instrumentors which seems the wrong way. What is your thoughts on this?

UPD Have proposed initial changes to the root instrumentors module via PR teppeis/empower-assert#3

Does power-assert provide descriptive assertion messages on browsers?

Code

assert(0 === 1);
assert.deepEqual({foo: 0}, {foo: 1});

Expected(node)

          assert(0 === 1)
                   |
                   false
  assert.deepEqual({ foo: 0 }, { foo: 1 })
                   |           |
                   |           Object{foo:1}
                   Object{foo:0}

Actual(browser)

          assert(0 === 1)
                   |
                   false
        AssertionError: {"foo":0} deepEqual {"foo":1}

when use the [email protected] from [email protected] / [email protected], doesn't have the deepStrictEqual, it seems old assert is used.

import assert from 'assert';
import moduleName from '../src';

describe('moduleName', () => {
  it('spec1', () => {
    assert.deepEqual(moduleName(), { foo: null });// pass
    assert.deepStrictEqual(moduleName(), { foo: null });// error
  });
});

simulation environment: https://github.com/59naga/boilerplate-browser-babel

git clone https://github.com/59naga/boilerplate-browser-babel
cd boilerplate-browser-babel
git checkout 4804fd5432c626268ca2f148bc58e15bed7c0ec5

npm install
node -v && npm -v
# v5.10.0
#3.8.3
npm test
# TypeError: _powerAssert2.default.deepStrictEqual is not a function
#        at Context.<anonymous> (/Users/59naga/Downloads/boilerplate-browser-babel/test/index.js:71:28 <- webpack:///test/index.js:10:11)

one workaround, frozen the version of assert in 4.1.2 using the core-assert.

npm install 59naga/power-assert
npm test
# ...
# AssertionError:   # test/index.js:11
#
#   assert.deepStrictEqual(moduleName(), { foo: null })
#                          |                 |
#                          |                 Object{foo:null}
#                          Object{foo:undefined}

other than this, would you have any good solution?

英語に自信がないので、翻訳前の日本語も残しておきます。
webpack/babel-loaderからpower-assertを使用すると、deepStrictEqualを持たない、古いassertが使用されるようです。
解決方法の一つとして、core-assertに依存し、assertのバージョンを4.1.2に固定する方法があります。
これ以外で、何か良い解決方法はご存知でしょうか？

I found with a surprise that assert.equal have both types as 'any' (even the strictEqual too):

export function equal(actual:any, expected:any, message?:string):void;

Why not do this way:

export function equal<T>(actual: T, expected: T, message?:string):void;

? It is better to catch any errors on compile time, not in the runtime, is not it?

It should let me know as errors.

assert(n === 0); // intended
assert(n = 0); // mistake, should be an error

Hello, and thank you for this wonderful library !

We use lab a lot for testing. And it's as easy to use Power-assert with lab that it is with mocha.

I'd like to share the transform file needed to activate Power-assert, and I wonder the best way to do it.
1- Do I create a project (like you did with espower-loader) under my account ?
2- Do you create an empty project, so I can send you a PR ?
3- Do I send you the file (20 lines) and instructions ?

Thank you again !

An assertion message has a local file path instead of variables.

expected:

assert(!!database_ === true);
       |||         |
       ||undefined false
       |true
       false

actual:

assert(!!dataD:/<dir>/<file>_ === true)
       |||         |
       ||undefined false
       |true
       false
...
... /power-assert.js:6093)

e.g. expect and should

We need to declare our official support policy.

refs #70

OUR SUPPORT POLICY

We support Node under maintenance. In other words, we stop supporting old Node version when their maintenance ends.
We also support modern browsers such as Chrome, Firefox, Safari, Edge etc.

This means that any other environment is not supported.

NOTE: If power-assert works in any of the unsupported environments, it is purely coincidental and has no bearing on future compatibility. Use at your own risk.

version: 1.4.1
SystemJS settings:

map = {
      "power-assert": "n:power-assert",
};
packages = {
   "power-assert": { main: "build/power-assert.js", defaultExtension: "js" },
}

My code

import * as assert from 'power-assert';

Which transpiles to:

var assert = require('power-assert');

And this line throws error:

Error: (SystemJS) Expected object
    TypeError: Expected object

Stack trace:

systemjs.src.js ~ line:3326

    if (exports && (exports.__esModule || exports instanceof Module))
      entry.esModule = loader.newModule(exports); // line:3326 <--- exports = function powerAssert ()
    // set module as 'default' export, then fake named exports by iterating properties
    else if (entry.esmExports && exports !== __global)
      entry.esModule = loader.newModule(getESModule(exports));
    // just use the 'default' export
    else
      entry.esModule = loader.newModule({ 'default': exports });

systemjs.src.js ~ line:892

    // 26.3.3.12
    newModule: function (obj) {
      if (typeof obj != 'object')
        throw new TypeError('Expected object'); // line:892 <!--- obj  = function powerAssert (), typeof obj = "function"

      var m = new Module();

Link to 26.3.3.12 of Loader-Spec
https://github.com/calvinmetcalf/Loader-Spec/blob/master/spec.md#263312-reflectloaderprototypenewmodule--obj-

obj is referencing to:

        powerAssert = function powerAssert () {
            return enhancement.apply(null, slice.apply(arguments));
        };

I prefer to use ts-node along with power assert, as I've already worked out how to get ts-node running the way I like.

I ran in to a few hurdles along the way, and created a new module to get ts-node working together with power-assert: https://github.com/tracecomms/espower-ts-node

The main thing I couldn't figure out was how to ignore errors and do a fast transpile instead of full type checking - which I find useful during dev, as it's quite a bit faster.

I know this is not really an issue as such, but though I'd add it here as I spent quite a bit of time trying to work this out, and hopefully either a) someone can let me know the simple solution I missed or b) this will help someone else!

Thanks for the amazing tool :-)

It seems that equals isn't always using strict equality:

assert.deepEqual({methodology: true}, {methodology: 1}) // doesn't fail
assert.equal(true, 1) // doesn't fail

Is it intended ?

describe("test", () => {
  const FOO = Symbol("FOO");
  const BAR = Symbol("BAR");
  const BAZ= Symbol("BAZ");

  let obj = {
    [FOO]: 100,
    [BAR]: 100,
    [BAZ]: 200,
  };

  it("works", () => {
    assert(obj[FOO] === obj[BAR]);
  });
  it("does not works", () => {
    // this test fails
    assert(obj[FOO] === obj[BAZ]);
  });
});

I expected:

1) test does not works:

  assert(obj[FOO] === obj[BAZ])
         |  ||    |   |  ||    
         |  ||    |   |  |Symbol(BAZ)
         |  ||    |   |  200   
         |  ||    |   Object{FOO:100,BAR:100,BAZ:200}
         |  ||    false        
         |  |Symbol(FOO)             
         |  100                
         Object{FOO:100,BAR:100,BAZ:200}

  [number] obj[BAZ]
  => 200
  [number] obj[FOO]
  => 100

but got:

  1) test does not works:
     TypeError: Cannot read property 'filter' of null
      at Array.forEach (native)
      at Context.<anonymous> (test/build.js:22:5)

test/a.js

 class A {
  constructor() {
    this.timer = setInterval(() => {}, 1000);
  }
}
const a = new A();
assert(a.timer);

index.js

'use strict';

require('intelli-espower-loader');
require('./test/a');

When I run node index.js, catch an error.

test/a.js:11
assert(a.timer);
       ^
ReferenceError: _rec1 is not defined
    at Object.<anonymous> (test/a.js:11:8)
    at Module._compile (module.js:570:32)
    at Object.extensions..js (/Users/gaoxiaochen/projj/github.com/node-modules/tcp-base/node_modules/.1.2.0@espower-loader/index.js:46:25)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/gaoxiaochen/projj/github.com/node-modules/tcp-base/index.js:2:1)
    at Module._compile (module.js:570:32)

I've created reproduce repository.

• https://github.com/azu/issue-power-assert-with-assert

Application code use assert module of Node Core.

index.js

// application code use `assert` module
const assert = require("assert");
export function hello(name) {
    assert(typeof name === "string");
    return "Hello " + name;
}

Test code:

const assert = require("power-assert");
import {hello} from "../src/index";
describe("hello", function () {
    it("should accept string", function () {
        hello(42);  // Should throw error via assert and fail tests.
    });
});

These code are transformed by babel + babel-plugin-espower.

.babelrc

{
  "presets": [
    "es2015"
  ],
  "env": {
    "development": {
      "plugins": [
        "babel-plugin-espower"
      ]
    }
  }
}

When I do this:

npm test

Expected

Fail test

Actual

Pass test :(

Reason

Application code is transformed to

"use strict";

Object.defineProperty(exports, "__esModule", {
    value: true
});

var _typeof = typeof Symbol === "function" && typeof Symbol.iterator === "symbol" ? function (obj) { return typeof obj; } : function (obj) { return obj && typeof Symbol === "function" && obj.constructor === Symbol ? "symbol" : typeof obj; };

var _powerAssertRecorder = function () { function PowerAssertRecorder() { this.captured = []; } PowerAssertRecorder.prototype._capt = function _capt(value, espath) { this.captured.push({ value: value, espath: espath }); return value; }; PowerAssertRecorder.prototype._expr = function _expr(value, source) { return { powerAssertContext: { value: value, events: this.captured }, source: source }; }; return PowerAssertRecorder; }();

exports.hello = hello;
// application code use `assert` module
var assert = require("assert");
function hello(name) {
    var _rec = new _powerAssertRecorder();

    assert(_rec._expr(_rec._capt(_rec._capt(typeof name === "undefined" ? "undefined" : _typeof(name), "arguments/0/left") === "string", "arguments/0"), {
        content: "assert(typeof name === \"string\")",
        filepath: "src/index.js",
        line: 4
    }));
    return "Hello " + name;
}
//# sourceMappingURL=index.js.map

_rec._expr return object.

    var assert = require("assert");
    var object = _rec._expr(_rec._capt(_rec._capt(typeof name === "undefined" ? "undefined" : _typeof(name), "arguments/0/left") === "string", "arguments/0"), {
        content: "assert(typeof name === \"string\")",
        filepath: "src/index.js",
        line: 4
    });
    assert(object);

So, assert(Object) never throw error. It causes this issue.

Do you have any solution?

Could you support the following usage? It is helpful for instant debugging.

assert.customize({ output: { maxDepth: 2 } }).deepEqual([[0]], [[1]]);

Probably because of breaking changes of dependencies.

https://travis-ci.org/falsandtru/power-assert/jobs/193616863
https://travis-ci.org/twada/power-assert-keeper/jobs/193616232

I would like to use assert.deepEqual() to compare two JSON objects, but the objects contain floating-point numbers that are only roughly the same. Is there some way to compare those two objects with a tolerance when comparing numbers? i.e. when the algorithm compares numbers it will accept a difference of up to 0.001% or something like that.

So, something like this is a pretty common pattern:

assert(typeof wrap === 'function')

    AssertionError:   # giraphe.es6.js:61

assert(typeof wrap === 'function')
       |           |
       "object"    false

--- [string] 'function'
+++ [string] typeof wrap
@@ -1,8 +1,6 @@
-function
+object


    + expected - actual

    -false
    +true

Although this works, I feel that this could easily be extended with more useful information: for instance, in most failing assertions, there's information about the object under test; but specifically in typeof's case, that gets lost, and it gets treated as a simple comparison of two static strings.

Here's something like what I'd expect to see (hastily cobbled together from the results for assert(wrap === 'function'), because it was an easy change :P:

    AssertionError:   # giraphe.es6.js:61

assert(typeof wrap === 'function')
       |      |    |
       |      |    false
       |      Object{}
       "object"

[string] 'function'
=> "function"
[Object] wrap
=> Object{}

--- [string] 'function'
+++ [string] typeof wrap
@@ -1,8 +1,6 @@
-function
+object


    + expected - actual

    -false
    +true

A function cannot assert own return value with no changes. I want the solution for it weak point.

Currently

• Need changes for postcondition(need temporary variable).
• Cannot provide descriptive assertion messages.

function add(a, b) {
  // precondition
  assert(typeof a === 'number' && isNaN(a));
  assert(typeof b === 'number' && isNaN(b));
  // return a + b;
  var ret = a + b;
  // postcondition
  assert(ret === b + a);
  return ret;
}

Method chaining

Not simple, not easy.

function add(a, b) {
  // precondition
  assert(typeof a === 'number' && isNaN(a));
  assert(typeof b === 'number' && isNaN(b));
  // postcondition and body
  return assert.return(a + b).equal(b + a);
}

Placeholder

Beautiful. Targeted for closest return statement only.

source:

function add(a, b) {
  // precondition
  assert(typeof a === 'number' && isNaN(a));
  assert(typeof b === 'number' && isNaN(b));
  // for all condition(however, code flow will be reversed)
  assert(assert.lookbehind === b + a); // => assert(a + b === b + a);
  // body
  return a + b;
  // postcondition
  assert(assert.lookahead === b + a); // => assert(a + b === b + a);
  assert(assert.lookahead === a + b); // => assert(a + b === a + b);
}

pre-espowered:

// Design A: Direct expansion
function add(a, b) {
  // precondition
  assert(typeof a === 'number' && isNaN(a));
  assert(typeof b === 'number' && isNaN(b));
  // for all condition(however, code flow will be reversed)
  assert(assert.lookbehind === b + a); // => assert(a + b === b + a);
  var actual = a + b; // any unique variable
  // postcondition
  // grouping
  assert(actual === b + a); // from lookbehind
  assert(actual === b + a); // from lookahead
  assert(actual === a + b); // from lookahead
  return actual;
}

// Design B: Use closure
function add(a, b) {
  // precondition
  assert(typeof a === 'number' && isNaN(a));
  assert(typeof b === 'number' && isNaN(b));
  // for all condition(however, code flow will be reversed)
  assert(assert.lookbehind === b + a); // => assert(a + b === b + a);
  // body
  return (function (actual) {
    // postcondition
    // grouping
    assert(actual === b + a); // from lookbehind
    assert(actual === b + a); // from lookahead
    assert(actual === a + b); // from lookahead
    return actual;
  })(a + b);
}

emit:

function add(a, b) {
  return a + b;
}

So cute 🍨 🌟 💓

assert("☺⛺✅㊗🆘🌀🌟🌾🍨🍬🍰🎃🎄🎍🎨🏃💞💤😭😒" === "☺⛺✅㊗🆘🌀🌟🌾🍨🍬🍰🎄🎍🎨🏃💞💤😭😒");

URIError: URI malformed
 at encodeURI (native)

good one:

bad one:

test with same file: power.js

var assert = require('assert');

describe('Array', function(){
    beforeEach(function(){
        this.ary = [1,2,3];
    });
    describe('#indexOf()', function(){
        it('should return index when the value is present', function(){
            var zero = 0, two = 2;
            assert(this.ary.indexOf(zero) === two);
        });
    });
});

I have one project that the test files are not in the test dir .

please help me. thanks!

Hi. I need to compare multiline strings but the output is too hard to analyze. It the a way to make it more visual. For example fast-diff seems interesting.

The second problem is compare on windows. When read input or output from disk it contains \r\n linebreaks. Every time I should to add .replace(/\r\n/g, '\n')

In mocha, the power-assert messages are displayed on both the stack and the message... it's a bit redundant.

global.assert = require('assert');
describe('test/showcase.test.js', () => {
  const arr = [ 1, 2, 3 ];

  it('power-assert', () => {
    assert(arr[1] === 10);
  });
});

then the unit test passed...

Is it possible to disable it? In this example, I'd like to see the first and third parts, just not the second part.

  assert(this.ary.indexOf(zero) === two)

              |   |       |     |   |
              |   |       |     |   2
              |   -1      0     false
              [1,2,3]

  [number] two
  => 2
  [number] this.ary.indexOf(zero)
  => -1

I tried to add this really simply to my vanilla Node.js module using intelli-espower-loader, but right from the jump I got this error: "TypeError: assert._capt is not a function"

Any root causes?

To reproduce, you can check out this repo at this commit: testdouble/scripty@4a00d0f

I have some tests that I'd like to run both in node and the browser. The tests are compiled using Babel (with babel/register to run in node, and with webpack's Babel loader for the browser).

My assumption was that I could just add babel-plugin-espower to my .babelrc plugins in order to apply the transformation for both cases. This worked, however, the browser build is including power-assert's dependencies, including acorn (some of which are causing webpack to generate build warnings). I think I understand why this is happening; my tests require power-assert, so naturally the dependencies are getting bundled.

So my question is, are all of the dependencies necessary at run time or are they just required for the transform? (If just for the transform is there a recommended way to omit them?)

I hope this is the right forum for this question! Thanks so much for such an awesome project!

class C {
  count_ = {};
  count() {
    return this.count_;
  }
}
var counter = new C();
assert(++counter.count_ === counter.count());

expected:

          assert(++counter.count_ === counter.count())
                 | |       |      |   |       |
                 | |       |      |   |       Object{}
                 | |       |      |   C{count_:#Object#}
                 | |       |      false
                 | |       Object{}
                 | C{count_:#Object#}
                 NaN

actual:

          assert(++counter.count_ === counter.count())
                 |                |   |       |
                 |                |   |       NaN
                 |                |   C{count_:NaN}
                 NaN              false

other:

          assert(+counter.count_ === counter.count())
                 ||       |      |   |       |
                 ||       |      |   |       Object{}
                 ||       |      |   C{count_:#Object#}
                 ||       |      false
                 ||       Object{}
                 |C{count_:#Object#}
                 NaN

I am trying to use power-assert to get pretty assert output in node, without using mocha or babel.

I'm trying to implement assertions by reading the documentation, but haven't been able to get it working so far.

Here is my attempt at a "vanilla node" (no mocha) seed: https://github.com/TehShrike/power-assert-espower-repro

entry point:

require('espower-loader')({
	pattern: 'test/*.js',
})

require('./test/test.js')

test/test.js:

const assert = require('power-assert')

const test = () => {
	const value1 = true
	const value2 = 3
	assert.deepEqual({ value: value1 }, { value: value2 })
}

test()

Instead of a nice pretty error message, I get:

/Users/josh/code/power-assert-espower-repro/node_modules/empower-core/lib/decorator.js:110
        ret = func.apply(thisObj, args);
                   ^
AssertionError: { value: true } deepEqual { value: 3 }
    at Decorator._callFunc (/Users/josh/code/power-assert-espower-repro/node_modules/empower-core/lib/decorator.js:110:20)
(snip)

What am I missing? I'm guessing this is a documentation/implementation issue, and not an actual bug.

(node 7.6.0)

$ $(npm bin)/mocha --require intelli-espower-loader ...
module.js:328
    throw err;
    ^

Error: Cannot find module 'espower-loader'

See power-assert-js/intelli-espower-loader#13

Just cross posting - power-assert-js/espower-typescript#18 hasn't been touched in over two weeks now. Can anyone here merge and publish it?

Hi, I just tried power-assert, it is looks great.

But I can't reproduce power-assert print, I have no idea why.

Could you give me some help?

  // It doesn't print
  assert(this.ary.indexOf(zero) === two)
              |   |       |     |   |
              |   |       |     |   2
              |   -1      0     false
              [1,2,3]

My package.json

{
  "name": "power-assert",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "devDependencies": {
    "@types/mocha": "^2.2.40",
    "@types/power-assert": "^1.4.29",
    "espower-typescript": "^8.0.0",
    "intelli-espower-loader": "^1.0.1",
    "mocha": "^3.2.0",
    "power-assert": "^1.4.2"
  },
  "scripts": {
    "test": "mocha --require intelli-espower-loader src/**/*.spec.js"
  }
}

index.spec.js

const assert = require('power-assert')

describe('Array', function() {
  describe('#indexOf()', function() {
    it('should return -1 when the value is not present', function() {
      assert(3 === [1, 2, 3].indexOf(4))
    })
  })
})

MacOS 10.12.4
node v6.9.1
yarn 0.20.3

code:

assert((-0, -1) === -0 + (-1));

expected:

  assert((-0, -1) + 1 === -0 + (-1))
         ||   |   |   |   |  |  |
         |0   -1  |   |   |  |  -1
         -1       |   |   0  -1
                  0   false

actual:

  assert((-0, -1) + 1 === -0 + -1)
                  |   |   |  | |
                  |   |   |  | -1
                  |   |   0  -1
                  0   false

So, for relatively simple assertions, it's possible to keep the entire assertion within the single assert( … ) statement; but I have a few places in my code where monstrosities like the following arise:

assert( null != blah.first_complicated_state() ?
   (null != blah.second_complicated_state() ?
      _.every(blah, element => ...)
    : _.every(blah, element => ...))
 : _.every(blah, element => ...)
)

Basically, sometimes, there's an expensive operation (i.e. not something I can safely leave laying around outside the assert, to end up in production code) that's necessary to choose how to assert something else.

Since I suspect asking for a to-be-compiled-out assert { … } block is unlikely to be in-line with the project goals, can I simply get a runtime-cheap boolean-property that I can test, to preform more complicated assertions that won't be compiled-out?

if (assert.enabled) {
   if (blah.first_complicated_state())
      assert( ... )

   else if (blah.second_complicated_state())
      assert( ... )
   ...
}

Async assertion is always successful under the this code.

    it('async assertion', function (done) {
      setTimeout(() => {
        console.log(assert(false === true), assert); // LOG: undefined, function powerAssert() { ... }
        done();
      }, 1);
    });

// gruntfile.js
    karma: {
      options: {
        configFile: 'karma.conf.js',
        preprocessors: {
          'test/fixture/*.html': ['html2js'],
          'test/cov/*.js': ['coverage', 'espower']
        }
      },
      ph: {
        browsers: ['PhantomJS'],
        singleRun: true
      },
      dev: {
        browsers: ['PhantomJS'],
        preprocessors: {
          'test/cov/*.js': ['espower']
        },
        singleRun: false
      }
    },

// karma.conf.js
    preprocessors: {
      'test/cov/*.js': ['coverage', 'espower']
    },

$ grunt karma:dev

以下詳細を英語がつたないので日本語で失礼します。
同期プロセスでのアサーションは正常に動作しますが非同期プロセスでは上記のとおりassert(false === true)が成功します。このバグは特殊な条件下で発生するようで、プリプロセッサの位置や組み合わせを変えると発生しません。grunt-karmaが内部的に生成するkarmaの設定が原因のような気がします。このバグが発生したプロダクトは未公開ですが対応していただけるようでしたら後ほど早めに公開してもってこようと思います。

expected

  assert(null instanceof Object)
              |          |
              false      #function#

  assert(void 0 instanceof Object)
         |      |          |
         |      false      #function#
         undefined

actual

  assert(null instanceof Object)
         |               |
         false           #function#

  assert(void 0 instanceof Object)
         |                 |
         |alse             #function#
         undefined

power-assert is amazing

windows 8, node v.0.11.13, power-assert 0.9.0
Runnig example test for node, mocha gives standart output without descriptive assertion messages.

assert(this.ary.indexOf(zero) === two)
                |   |       |     |   |
                |   |       |     |   2
                |   -1      0     false
                [1,2,3]

^ I don't see it.
What am I doing wrong?

power-asserted test result includes filepath with 'full path' like this.

assert.strictEqual(assert._expr(assert._capt(typeof res, 'arguments/0'), {
  content: 'assert.strictEqual(typeof name, \'string\')',
  filepath: '/home/username/path/to/project/and/file.js',
  line: 22
}), 'string');

file path with full path is kind of sensitive information in server or developer machine.
if user doesn't know this behavior, it may cause some security issue.
(for example, some could forgot adding build result to gitignore and push to public repository.)

I think this information is only a project specific.
so it seems better for me to use relative path of test file or project or configurable base bath.

any comments ?

test/a.js

'use strict';

const assert = require('assert');

class AMap extends Map {
  get(name) {
    console.log(name);
    return super.get(name);
  }
}
const map = new AMap();
map.set('a', true);
assert(map.has('a'));

index.js

'use strict';

require('intelli-espower-loader');
require('./test/a.js');

When I run node index.js, catch an error.

test/a.js:13
assert(map.has('a'));
       ^
ReferenceError: _rec1 is not defined
    at Object.<anonymous> (test/b.js:13:8)
    at Module._compile (module.js:570:32)
    at Object.extensions..js (/Users/popomore/code/tmp/b/node_modules/.1.2.0@espower-loader/index.js:46:25)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/popomore/code/tmp/b/index.js:4:1)
    at Module._compile (module.js:570:32)

There seems to be lacking output for assert.deepStrictEqual compared to assert.deepEqual.
If you provide a 'descriptive message when assertion is failed' only that message will be printed:

descriptive message

If you don't provide a message to the method, the compared objects will be printed like this:

{object1} deepStrictEqual {object2}

But in both cases you want to be able to compare them in the output (somewhat like deepEqual).

Besides this if the objects (that are compared) are somewhat 'big' they wont display completely (when not providing a message):

{"startupExtent":{"extent":[139722.24000000002,407339.51999999996,159774.72,416102.39999999997],"srs":"EPSG:28992"},"userSrs":"E deepStrictEqual {"startupExtent":{"extent":[139722.24000000002,407339.51999999996,159774.72,416102.39999999997],"srs":"EPSG:28992"},"userSrs":"E

actual object:
var object = { startupExtent: {"extent":[139722.24000000002,407339.51999999996,159774.72,416102.39999999997],"srs":"EPSG:28992"}, userSrs: 'EPSG:28992', searchHistory: [], mapShowScaleBarDefault: true, mapShowZoomSliderDefault: true, }

Hi Lions!

In my karma plugin, I'm testing customized options only by comparing stdout with passed options, so it would be nice if I can access to the options I passed though assert.customize, to develop plugins in my case. It can be something like assert.options to return extend(empowerOptions, options.assertion) I guess.

• https://github.com/watilde/karma-power-assert/blob/master/karma.conf.js#L9-L15
• https://github.com/watilde/karma-power-assert/blob/master/test/adapter.spec.js#L14-L32

Any plans or thoughts?

can we get fancy diff while deepEqual-ing two arrays?

right now, it's not neither fancy, neither helpful at all

  1. index › should esDepsResolved

  t.deepEqual(_, expected)
              |  |
              |  [#Object#,#Object#,#Object#,#Object#,#Object#,#Object#]
              [#Object#,#Object#,#Object#,#Object#,#Object#,#Object#]

      resolved: '/Users
        Decorator._callFunc (/Users/iamstarkov/projects/es-deps-resolved/node_modules/.store/[email protected]/_/lib/decorator.js:110:20)
        Decorator.concreteAssert (/Users/iamstarkov/projects/es-deps-resolved/node_modules/.store/[email protected]/_/lib/decorator.js:103:17)
        Object.decoratedAssert [as deepEqual] (/Users/iamstarkov/projects/es-deps-resolved/node_modules/.store/[email protected]/_/lib/decorate.js:49:30)
        index.js:29:7

so, i have to do

  .then(_ => {
    t.deepEqual(_[0], expected[0]);
    t.deepEqual(_[1], expected[1]);
    t.deepEqual(_[2], expected[2]);
    t.deepEqual(_[3], expected[3]);
    t.deepEqual(_[4], expected[4]);
    t.deepEqual(_[5], expected[5]);
  }));

instead of just this

  .then(_ => t.deepEqual(_, expected)));

I absolutely love, love, love power-assert.

One thing I'm a bit unsure about is how to test promises, though. In chai, for example, I can do

expect(promise).to.be.rejectedWith(...)

but with power-assert I need much more code. Is adding higher-level assertions on the roadmap, or can I build these myself somehow?

Reference:
avajs/ava#274