avajs/ava

Report all assertion failures

Open

#261 opened on Nov 23, 2015

View on GitHub
 (18 comments) (1 reaction) (0 assignees)JavaScript (20,600 stars) (1,408 forks)batch import
enhancementhelp wantedscope:assertionsscope:reporters

Description

With #259, we have moved from only printing the last assertion failure, to only printing the first.

Once #243 (chainable methods) happens, I think we should allow printing of every failed assertion to give the most information possible.

test.verbose('title', t => {
  t.fail('a');
  t.fail('b');
});

Perhaps only mode should also just imply verbose mode (you should have way less noise with a single test).

Contributor guide

Tech stack
javascript
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of AVA testing frameworkFamiliarity with assertion handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate how AVA currently reports assertion failures after PR #259, which changed from printing last to first failure. Look at the test runner and reporter modules (e.g., lib/runner.js or lib/reporters/) to understand the failure collection logic. The goal is to modify the code to iterate over all failures and print each, possibly controlled by a verbose flag. Also consider the impact of chainable methods (#243) and ensure that `only` mode triggers verbose output. There are no open PRs, so work can start fresh.