You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unit tests often include many logs that can provide insight on what's happening in that test. In JavaScript, console logs are generally divided into four levels:
debug
info (this is generally the default used by console.log)
warn
error
If you are running a full test suite, you're likely to be most interested in error logs, because they will be the ones that show you which tests are failing and why. If you're running or debugging an individual test, you're more likely to be interested in all logs.
Problem
When running our jest tests, the large volume of logs across all tests makes it difficult to quickly see which tests failed and why. This prevents us from quickly resolving issues when tests fail on a PR, which in turn can delay the merge and deploy of the PR.
Solution
Silence debug, info, and warn logs by default in our jest tests. This will greatly reduce the volume of logs and make it easier to quickly identify which tests failed and why. Enable developers to see all log levels by passing the --verbose flag to jest; that way we can still dive into more detail in an individual test for debugging purposes.
This issue has not been updated in over 15 days. @mananjadhav, @elirangoshen eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
Activity
mananjadhav commentedon Sep 20, 2025
PR being reviewed and worked upon.
mananjadhav commentedon Sep 27, 2025
Left review, waiting for it to be picked up again.
melvin-bot commentedon Oct 22, 2025
This issue has not been updated in over 15 days. @mananjadhav, @elirangoshen eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
mananjadhav commentedon Oct 26, 2025
@roryabraham I had helped with the review of the PR and it's now deployed in production for ~2 weeks. Can you help with the payment summary?
5 remaining items
melvin-bot commentedon Oct 28, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021983296236419899384
melvin-bot commentedon Oct 28, 2025
Current assignee @mananjadhav is eligible for the External assigner, not assigning anyone new.
melvin-bot commentedon Oct 28, 2025
Triggered auto assignment to @RachCHopkins (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.roryabraham commentedon Oct 28, 2025
@RachCHopkins just a standard $250 C+ review bounty to @mananjadhav
RachCHopkins commentedon Oct 31, 2025
Payment Summary:
Upwork job here
RachCHopkins commentedon Oct 31, 2025
No contributor to pay via upwork, and the Upwork post has been closed.
🟢 to @mananjadhav to request payment.
quinthar commentedon Nov 2, 2025
$250 approved to @mananjadhav