-
Notifications
You must be signed in to change notification settings - Fork 916
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Test] Investigate console warnings in field_editor.test.tsx #673
Comments
ananzh
added a commit
to ananzh/OpenSearch-Dashboards
that referenced
this issue
Jul 27, 2021
Currently, unit test field_editor.test.tsx shows a console warning: ```React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. ``` This warning is because EuiCodeEditor is missing in the mock of elastic/eui, which causes undefined EuiCodeEditor in the test. PR Resolved: opensearch-project#673 Signed-off-by: Anan Zhuang <[email protected]>
5 tasks
ananzh
added a commit
to ananzh/OpenSearch-Dashboards
that referenced
this issue
Jul 29, 2021
Currently, unit test field_editor.test.tsx shows a console warning: ```React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. ``` This warning is because EuiCodeEditor is missing in the mock of elastic/eui, which causes undefined EuiCodeEditor in the test. PR Resolved: opensearch-project#673 Backport PR: opensearch-project#674 Signed-off-by: Anan Zhuang <[email protected]>
5 tasks
ananzh
added a commit
that referenced
this issue
Jul 29, 2021
Currently, unit test field_editor.test.tsx shows a console warning: ```React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. ``` This warning is because EuiCodeEditor is missing in the mock of elastic/eui, which causes undefined EuiCodeEditor in the test. PR Resolved: #673 Backport PR: #674 Signed-off-by: Anan Zhuang <[email protected]>
tmarkley
pushed a commit
to tmarkley/OpenSearch-Dashboards
that referenced
this issue
Aug 3, 2021
Previous PR opensearch-project#674 did not include updated snapshots. Related to opensearch-project#673 Signed-off-by: Tommy Markley <[email protected]>
tmarkley
pushed a commit
that referenced
this issue
Aug 4, 2021
Previous PR #674 did not include updated snapshots. Related to #673 Signed-off-by: Tommy Markley <[email protected]>
tmarkley
pushed a commit
to tmarkley/OpenSearch-Dashboards
that referenced
this issue
Aug 5, 2021
Previous PR opensearch-project#674 did not include updated snapshots. Related to opensearch-project#673 Signed-off-by: Tommy Markley <[email protected]>
tmarkley
pushed a commit
that referenced
this issue
Aug 6, 2021
Previous PR #674 did not include updated snapshots. Related to #673 Signed-off-by: Tommy Markley <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue
Currently,
field_editor.test.tsx
prints out console warnings when run the unit test. To make a clean unit test, we want to explore the reasons for these errors/warnings and decide whether we could fix or remove them.To Reproduce
Run:
yarn test:jest {path to field_editor.test.tsx}
Expected behavior
explore each problem unit test cases and investigate each question:
what causes the console error or issues?
should this unit test log this error or warning message?
if answer to the above question is no, then can we fix it?
The final output is expected to be a cleaned unit test with un-necessary error/warnings been removed.
OpenSearch Version
OpenSearch 1.0.0
Dashboards Version
Dashboards 1.0.0
The text was updated successfully, but these errors were encountered: