FoamFactory / FoamFactory/taphandle
console.warn statements that occur during tests should be encapsulated and tested
Open
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The `console.warn` statements that occur (and are expected to occur) during testing should be wrapped in another function, and this function should be used to check whether a specific statement occurred or not. The default should be that _no_ `console.warn` statements should be printed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the console.warn statements and the tests that trigger them. Encapsulate expected warnings behind a test helper and verify that expected warnings are checked while no unexpected console.warn output is printed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100