Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

Jest warnings #3603

Closed
sdadn opened this issue Mar 30, 2022 · 2 comments
Closed

Jest warnings #3603

sdadn opened this issue Mar 30, 2022 · 2 comments
Labels
help wanted inactive Jira Created
Milestone
Backlog

Comments

@sdadn
Copy link
Contributor

sdadn commented Mar 30, 2022

Description

As a developer, I would like to clean up the jest warnings caused by outdated tests, so that the output is cleaner and doesn't bury any legitimate output. We'll know we're done when there are no more jest warnings.

Steps to Reproduce

  1. Run npm run compile && npm run jest on the main branch
  2. The jest tests will output warnings

Additional Context / Screenshots

CleanShot 2022-03-30 at 13 14 51
@chrismichalewicz
Copy link

UXPLATFORM-6602 was logged to track this internally

@xenoworf xenoworf added this to the Backlog milestone May 24, 2022
@stale
Copy link

stale bot commented Jul 23, 2022

This issue has been automatically marked as inactive because it has not had recent activity. It will be closed in seven days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the inactive label Jul 23, 2022
@stale stale bot closed this as completed Jul 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
help wanted inactive Jira Created
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@sdadn @xenoworf @chrismichalewicz