Docs: Really, use `t` for assertions

I just tried to covert a project that’s tested with tape over to using AVA instead. The tests all follow this kind of format:

test('function-a', (assert) => {
  assert.plan(1);

  assert.is(
    functionA(),
    resultB,
    'function a should return result b'
  );
});

They seem to run just fine under AVA, but the assertion messages don’t show up when I create a failing test case, just the test messages.

Is there a way to report on the assertion messages? Or is the best practice just to wrap every one of these assertions in its own test block? (In which case, why do the assertions accept optional message parameters?

Am I missing something stupid?

[smeijer]

Try using t instead of assert as your parameter name (using t should enable power-assert).

I had this exact same issue. I guess it’s worth a note in the readme, perhaps under FAQ.

Why is the power-assert information not shown?

Try using t instead as your parameter name.

This is a byproduct of the way power-assert works. It uses a pattern matching scheme that makes it easier for implementors to wrap any assertion library with power-assert goodness without having to understand the ES AST at all

[jamestalmage]

Really?

It seems to work, but that’s kinda voodoo.

Yes, yes it is. This is a byproduct of the way power-assert works. It uses a pattern matching scheme that makes it easier for implementors to wrap any assertion library with power-assert goodness without having to understand the ES AST at all (which is super awesome). That said, the AVA team certainly has members capable of creating a more robust matcher that would detect your use of a different variable name, so if power-assert exposed an “advanced” API, we could certainly leverage it to provide a more user friendly experience.

See https://github.com/power-assert-js/babel-plugin-espower/issues/18.

It would be non-trivial, but something worth doing.