Horizontal rule between successful runs with logs

[jamiebuilds]

In watch mode, if you log something in your code while working on tests, it will look like this:

# ... previous failures ...
─────────────────────────────────────
'logged value'

  1 passed [11:44:22]

On the next run it will look like this:

# ... previous failures ...
─────────────────────────────────────
'logged value'
'logged value'

  1 passed [11:44:32]

This is okay for small values like 'logged value', but when you are logging lots of things including large objects it would be nice for some visual separation.

What if AVA added another horizontal rule in between sets of logs?

# ... previous failures ...
─────────────────────────────────────
'logged value'
─────────────────────────────────────
'logged value'

  1 passed [11:44:32]

This would make it much more clear what run the logs were from.

There is a $40.00 open bounty on this issue. Add more on Issuehunt.

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on Issuehunt to raise funds.

[novemberborn]

What do you mean by "log"? stdout / stderr?

I think it may be less confusing if you use verbose mode, IIRC that always writes the separator. But maybe this makes sense for the default mode. It's just that the reporters are a bit of a mess.

[jamiebuilds]

I mean console.log, but I'm assuming AVA already has pipes of all the user's stdout/stderr and can detect if they wrote anything.

[novemberborn]

Yea, makes sense.

I tried to figure out how this stuff currently works and I couldn't in a reasonable amount of time. Will add the appropriate labels and leave this open, but it may be something to be done as part of #1776.

[IssueHuntBot]

@IssueHunt has funded $40.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[yovasx2]

I think you can only wrap your logged object in a couple of rulers:

console.log("___________________________")
console.log(big_obj); 
console.log("___________________________")

[yovasx2]

Also we cannot fix this since t.log() is broken for mini reporter: #2201

[m5x5]

@novemberborn You referenced this issue in #2217, but it seems like this enhancement isn't related to #2217, isn't it? I feel like this issue should be marked as blocked, since we cannot work on this issue, as long we haven't closed #2217.

[novemberborn]

@Michael55555 sure, thanks.

[novemberborn]

Both due to the age of this issue, and the state of our reporters, I've decided to roll this into #2501.