Jest test output is too big because of console logging #10682
Labels
component:code_quality
component:testing
migration:no-jira
migration:2024
qa:not_needed
repository:addons-frontend
Issue relating to addons-frontend
triaged
Milestone
This has been happening realistically since Jest but I think the bundle size has made it more intense. Basically our test output is so huge that Travis stops rendering it and it makes looking up failed tests quite difficult.
I don't think there's an easy fix but I'm filing this here because having to download the raw logs for failing tests is pretty annoying and locally I'll often run
yarn test -- --silent
because otherwise it's way too loud.We should fix things up so test output, especially on Travis, is nice and concise so we can see–at a glance–test failures.
The text was updated successfully, but these errors were encountered: