Spurred by conversation in avajs/ava#2449 and avajs/ava#1485 we'd like for our assertions to return booleans. true when they pass, false when they fail. This does not apply to the throws() and throwsAsync() assertions.

Failing assertions will fail the test, but do not throw exceptions. This means your test does not stop executing. Usua

This is meant as a discussion to follow up on #411. For those interested in getting more involved with goss, I am interested in the following:

1. Now that there is a CONTRIBUTING.md, issue/pr templates,

If you comment out test cases with a here-doc like

: <<EOC
@test 'to be ignored for now' {
}
EOC

this greatly confuses bats-core.
As far as I have seen from a very quick look, you pre-process the test file line-wise.
So every line that looks like a test, even if just part of a multi-line string or here-doc will be considered a test case and confuse bats-core later on.

The README for nyc states:

Please start with the pre-configured @istanbuljs/nyc-config-babel preset [...]

The README for nyc-config-babel states:

Handy default configuration for instrumenting your babel-backed project [...]

When I configure my babel project without this package, everything seems to work correctly. None of the documentation I've found explains why I should pull in t

Hey,

Im going through examples in readme and in https://volument.com/baretest but as far as i can tell, just copy pasting them throws errors.

It would be nice to have a repo to clone to:

1. see how to set it up. currently i dont understand what this supposed to be const test = require('.')('sum'), in docs. And its not lack of my js knowledge that bothers me.
2. verify the performance cl

Running the following test file should report a failure but does not:

// error.js
const {test} = require('zora')

test('error message with string', t => {
  t.throws(() => { throw new Error('message') }, 'another message')
})

Output:

$ node error.js 
TAP version 13
# error message with string
ok 1 - another message
1..1

# ok
# success: 1
# skipped: 0
# failure:

If you upgraded to the latest version, you'll need to make some adjustments. Sorry! 🙇

In this issue, I'll explain what these changes are and how to rewrite your tests.

History

Let's make sure we are on the same page. The previous test syntax wasn't valid fish syntax. Running fishtape test.fish transformed test blocks to valid to [test](https://fishshell.com/docs/current/commands.

With the browserify command, all gets bundled and in case of an error, it does not point to the correct line number of the source code. Is there a trick to make this happen?

This tap allows for casks to be upgraded based on their version. Adding an :upgrade action to the casks provider would significantly improve the quality of the homebrew cookbook.