Metadata
Description
Simon Bates pointed out in recent meetings that our test output is hard to parse because. of the various warnings and console output that clutters the results. In this ticket, I will work to get as close as we can to only displaying test results.
Comments
-
Tony Atkins [RtF] commented
2021-04-21T05:53:30.688-0400 Just to document the "rogue's gallery", from top to bottom, the first "noise" is in the AudioManagerImpl tests:
PASS src/AudioManagerImpl.test.js ... * Tone.js v14.7.77 * ... | | A -3 | A -2 | A -1 | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | Q +1 | Q +2 | Q +3 |The next bit is in the Character tests:
PASS src/Character.test.js ... Warning: The tag <g> is unrecognized in this browser. If you meant to render a React component, start its name with an uppercase letter.There's a slightly disturbing warning in the ProgramBlockEditor tests, which suggests that we might be trying to announce nothing:
PASS src/ProgramBlockEditor.test.js ... * Tone.js v14.7.77 * ... Error: [@formatjs/intl Error MISSING_TRANSLATION] Missing message: "Announcement." for locale "en", using id as fallback. ... Warning: Failed prop type: You provided a `value` prop to a form field without an `onChange` handler. This will render a read-only field. If the field should be mutable use `defaultValue`. Otherwise, set either `onChange` or `readOnly`.The ProgramBlockEditor tests also have that "value" warning.
-
Tony Atkins [RtF] commented
2021-04-21T06:59:22.085-0400 There's a lightly documented option to disable the Tone messages, but I can't figure out how to get it to work with our stack. I can't seem to import Tone in a way that exposes the flag there. Simon Bates or Daniel Cho, any suggests on Jest setup steps, etc. would be appreciated.
-
Tony Atkins [RtF] commented
2021-04-21T07:14:43.693-0400 We may have to live with the "g" warnings, unless you we can find a way to disable them:
https://stackoverflow.com/questions/47774410/svg-components-raise-a-warning/51916014