-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log tests as soon as they start #1084
Labels
question
RR - refactor & re-engineer
Results in an improvement to developers using Marked, or end-users, or both.
Comments
joshbruce
added
RR - refactor & re-engineer
Results in an improvement to developers using Marked, or end-users, or both.
question
labels
Feb 26, 2018
Would be nice to also add test time to the output. something like:
|
@davisjam did some really nice updates - think the foundations are in place once we get that merged in should just be a matter of strings and a timer?? |
davisjam
added a commit
to davisjam/marked
that referenced
this issue
Feb 26, 2018
Problem: On hangs, test output is hard to read. Solution: Print test name before starting. Bonus: Also print an approximation of how long each test takes to run. For markedjs#1084.
zhenalexfan
pushed a commit
to zhenalexfan/MarkdownHan
that referenced
this issue
Nov 8, 2021
Problem: On hangs, test output is hard to read. Solution: Print test name before starting. Bonus: Also print an approximation of how long each test takes to run. For markedjs#1084.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
question
RR - refactor & re-engineer
Results in an improvement to developers using Marked, or end-users, or both.
Marked version: 0.3.16
Proposal type: new feature
What pain point are you perceiving?
Was interacting with @davisjam on #1083 and related issues. There were two tests created for the REDOS check. I wasn't sure which test had actually experienced the DOS.
What solution are you suggesting?
I think the tests run in alphabetical order. If so, it would have been the second test that failed, not the first. Therefore, curious if we could console log as soon as the test starts - when they fail, new lines are created anyway; so, not sure the cost benefit analysis is there for have them on one line.
The text was updated successfully, but these errors were encountered: