Add t.before(fn) method by isaacs · Pull Request #28 · tapjs/libtap

isaacs · 2021-02-16T08:02:51Z

Based on #27, land that first.

While the recommendation in the past has been 'use t.test() for this',
it's really annoying to have to specify -g 'setup|my test' when
running a single test for debugging. Also, you might not want to have
assertions for these; often just a simple pass/fail is enough, and can
keep the test output a bit quieter.

t.before(fn) is effectively a single (optionally promise-returning)
function which can be run before all tests and assertions, and which is
immune to any filters.

If the t.before(fn) function throws or rejects, is called more than
once, or is called after any tests or assertions, then the test fails.

While the recommendation in the past has been 'use t.test() for this', it's really annoying to have to specify `-g 'setup|my test'` when running a single test for debugging. Also, you might not want to have assertions for these; often just a simple pass/fail is enough, and can keep the test output a bit quieter. `t.before(fn)` is effectively a single (optionally promise-returning) function which can be run before all tests and assertions, and which is immune to any filters. If the `t.before(fn)` function throws or rejects, is called more than once, or is called after any tests or assertions, then the test fails.

coreyfarrell · 2021-02-16T14:05:35Z

Side note I'm really liking TLA in ESM based tests for this purpose.

isaacs · 2021-02-16T08:02:51Z

Based on #27, land that first.

While the recommendation in the past has been 'use t.test() for this',
it's really annoying to have to specify -g 'setup|my test' when
running a single test for debugging. Also, you might not want to have
assertions for these; often just a simple pass/fail is enough, and can
keep the test output a bit quieter.

t.before(fn) is effectively a single (optionally promise-returning)
function which can be run before all tests and assertions, and which is
immune to any filters.

If the t.before(fn) function throws or rejects, is called more than
once, or is called after any tests or assertions, then the test fails.

While the recommendation in the past has been 'use t.test() for this', it's really annoying to have to specify `-g 'setup|my test'` when running a single test for debugging. Also, you might not want to have assertions for these; often just a simple pass/fail is enough, and can keep the test output a bit quieter. `t.before(fn)` is effectively a single (optionally promise-returning) function which can be run before all tests and assertions, and which is immune to any filters. If the `t.before(fn)` function throws or rejects, is called more than once, or is called after any tests or assertions, then the test fails.

coreyfarrell · 2021-02-16T14:05:35Z

Side note I'm really liking TLA in ESM based tests for this purpose.

isaacs · 2021-02-16T08:02:51Z

Based on #27, land that first.

While the recommendation in the past has been 'use t.test() for this',
it's really annoying to have to specify -g 'setup|my test' when
running a single test for debugging. Also, you might not want to have
assertions for these; often just a simple pass/fail is enough, and can
keep the test output a bit quieter.

t.before(fn) is effectively a single (optionally promise-returning)
function which can be run before all tests and assertions, and which is
immune to any filters.

If the t.before(fn) function throws or rejects, is called more than
once, or is called after any tests or assertions, then the test fails.

While the recommendation in the past has been 'use t.test() for this', it's really annoying to have to specify `-g 'setup|my test'` when running a single test for debugging. Also, you might not want to have assertions for these; often just a simple pass/fail is enough, and can keep the test output a bit quieter. `t.before(fn)` is effectively a single (optionally promise-returning) function which can be run before all tests and assertions, and which is immune to any filters. If the `t.before(fn)` function throws or rejects, is called more than once, or is called after any tests or assertions, then the test fails.

coreyfarrell · 2021-02-16T14:05:35Z

Side note I'm really liking TLA in ESM based tests for this purpose.

isaacs · 2021-02-16T08:02:51Z

Based on #27, land that first.

While the recommendation in the past has been 'use t.test() for this',
it's really annoying to have to specify -g 'setup|my test' when
running a single test for debugging. Also, you might not want to have
assertions for these; often just a simple pass/fail is enough, and can
keep the test output a bit quieter.

t.before(fn) is effectively a single (optionally promise-returning)
function which can be run before all tests and assertions, and which is
immune to any filters.

If the t.before(fn) function throws or rejects, is called more than
once, or is called after any tests or assertions, then the test fails.

While the recommendation in the past has been 'use t.test() for this', it's really annoying to have to specify `-g 'setup|my test'` when running a single test for debugging. Also, you might not want to have assertions for these; often just a simple pass/fail is enough, and can keep the test output a bit quieter. `t.before(fn)` is effectively a single (optionally promise-returning) function which can be run before all tests and assertions, and which is immune to any filters. If the `t.before(fn)` function throws or rejects, is called more than once, or is called after any tests or assertions, then the test fails.

coreyfarrell · 2021-02-16T14:05:35Z

Side note I'm really liking TLA in ESM based tests for this purpose.

isaacs · 2021-02-16T08:02:51Z

Based on #27, land that first.

While the recommendation in the past has been 'use t.test() for this',
it's really annoying to have to specify -g 'setup|my test' when
running a single test for debugging. Also, you might not want to have
assertions for these; often just a simple pass/fail is enough, and can
keep the test output a bit quieter.

t.before(fn) is effectively a single (optionally promise-returning)
function which can be run before all tests and assertions, and which is
immune to any filters.

If the t.before(fn) function throws or rejects, is called more than
once, or is called after any tests or assertions, then the test fails.

While the recommendation in the past has been 'use t.test() for this', it's really annoying to have to specify `-g 'setup|my test'` when running a single test for debugging. Also, you might not want to have assertions for these; often just a simple pass/fail is enough, and can keep the test output a bit quieter. `t.before(fn)` is effectively a single (optionally promise-returning) function which can be run before all tests and assertions, and which is immune to any filters. If the `t.before(fn)` function throws or rejects, is called more than once, or is called after any tests or assertions, then the test fails.

coreyfarrell · 2021-02-16T14:05:35Z

Side note I'm really liking TLA in ESM based tests for this purpose.

isaacs · 2021-02-16T08:02:51Z

Based on #27, land that first.

While the recommendation in the past has been 'use t.test() for this',
it's really annoying to have to specify -g 'setup|my test' when
running a single test for debugging. Also, you might not want to have
assertions for these; often just a simple pass/fail is enough, and can
keep the test output a bit quieter.

t.before(fn) is effectively a single (optionally promise-returning)
function which can be run before all tests and assertions, and which is
immune to any filters.

If the t.before(fn) function throws or rejects, is called more than
once, or is called after any tests or assertions, then the test fails.

While the recommendation in the past has been 'use t.test() for this', it's really annoying to have to specify `-g 'setup|my test'` when running a single test for debugging. Also, you might not want to have assertions for these; often just a simple pass/fail is enough, and can keep the test output a bit quieter. `t.before(fn)` is effectively a single (optionally promise-returning) function which can be run before all tests and assertions, and which is immune to any filters. If the `t.before(fn)` function throws or rejects, is called more than once, or is called after any tests or assertions, then the test fails.

coreyfarrell · 2021-02-16T14:05:35Z

Side note I'm really liking TLA in ESM based tests for this purpose.

isaacs · 2021-02-16T08:02:51Z

Based on #27, land that first.

While the recommendation in the past has been 'use t.test() for this',
it's really annoying to have to specify -g 'setup|my test' when
running a single test for debugging. Also, you might not want to have
assertions for these; often just a simple pass/fail is enough, and can
keep the test output a bit quieter.

t.before(fn) is effectively a single (optionally promise-returning)
function which can be run before all tests and assertions, and which is
immune to any filters.

If the t.before(fn) function throws or rejects, is called more than
once, or is called after any tests or assertions, then the test fails.

While the recommendation in the past has been 'use t.test() for this', it's really annoying to have to specify `-g 'setup|my test'` when running a single test for debugging. Also, you might not want to have assertions for these; often just a simple pass/fail is enough, and can keep the test output a bit quieter. `t.before(fn)` is effectively a single (optionally promise-returning) function which can be run before all tests and assertions, and which is immune to any filters. If the `t.before(fn)` function throws or rejects, is called more than once, or is called after any tests or assertions, then the test fails.

coreyfarrell · 2021-02-16T14:05:35Z

Side note I'm really liking TLA in ESM based tests for this purpose.

isaacs · 2021-02-16T08:02:51Z

Based on #27, land that first.

While the recommendation in the past has been 'use t.test() for this',
it's really annoying to have to specify -g 'setup|my test' when
running a single test for debugging. Also, you might not want to have
assertions for these; often just a simple pass/fail is enough, and can
keep the test output a bit quieter.

t.before(fn) is effectively a single (optionally promise-returning)
function which can be run before all tests and assertions, and which is
immune to any filters.

If the t.before(fn) function throws or rejects, is called more than
once, or is called after any tests or assertions, then the test fails.

While the recommendation in the past has been 'use t.test() for this', it's really annoying to have to specify `-g 'setup|my test'` when running a single test for debugging. Also, you might not want to have assertions for these; often just a simple pass/fail is enough, and can keep the test output a bit quieter. `t.before(fn)` is effectively a single (optionally promise-returning) function which can be run before all tests and assertions, and which is immune to any filters. If the `t.before(fn)` function throws or rejects, is called more than once, or is called after any tests or assertions, then the test fails.

coreyfarrell · 2021-02-16T14:05:35Z

Side note I'm really liking TLA in ESM based tests for this purpose.

coreyfarrell force-pushed the isaacs/before-fn branch from a9ad541 to a75fe4cCompare February 16, 2021 13:55

coreyfarrell merged commit 7fdd8be into masterFeb 16, 2021

coreyfarrell deleted the isaacs/before-fn branch February 16, 2021 14:05