Skip to content
Unit Testing

Updated version of lexical packages #4387

Sign in to view logs

Updated version of lexical packages

Updated version of lexical packages #4387

Triggered via pull request August 7, 2024 04:24
@akanshaaa19akanshaaa19
opened #3010
lexical-update
Status Failure
Total duration 4m 25s
Artifacts –

unit-testing.yml

on: pull_request
CI
4m 14s
CI
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
src/containers/InteractiveMessage/InteractiveMessage.test.tsx > Add mode > it renders empty interactive form: src/containers/InteractiveMessage/InteractiveMessage.test.tsx#L169
TestingLibraryElementError: Unable to find an element by: [data-testid="addButton"] Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/InteractiveMessage/InteractiveMessage.test.tsx:169:11
src/containers/InteractiveMessage/InteractiveMessage.test.tsx > Add mode > it validates url: src/containers/InteractiveMessage/InteractiveMessage.test.tsx#L277
TestingLibraryElementError: Unable to find an element with the text: Add a new Interactive message. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/InteractiveMessage/InteractiveMessage.test.tsx:277:11
src/containers/InteractiveMessage/InteractiveMessage.test.tsx > Add mode > It creates a interactive message with dynamic content: src/containers/InteractiveMessage/InteractiveMessage.test.tsx#L295
TestingLibraryElementError: Unable to find an element with the text: Marathi. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/InteractiveMessage/InteractiveMessage.test.tsx:295:11
src/containers/InteractiveMessage/InteractiveMessage.test.tsx > Edit mode > it renders quick reply in edit mode and changes language: src/containers/InteractiveMessage/InteractiveMessage.test.tsx#L319
TestingLibraryElementError: Unable to find an element with the text: Title. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/InteractiveMessage/InteractiveMessage.test.tsx:319:11
src/containers/InteractiveMessage/InteractiveMessage.test.tsx > Edit mode > it renders interactive list in edit mode: src/containers/InteractiveMessage/InteractiveMessage.test.tsx#L348
TestingLibraryElementError: Unable to find an element with the text: Save. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/InteractiveMessage/InteractiveMessage.test.tsx:348:11
src/containers/InteractiveMessage/InteractiveMessage.test.tsx > location request message > it renders empty location request message: src/containers/InteractiveMessage/InteractiveMessage.test.tsx#L366
TestingLibraryElementError: Unable to find an element by: [data-testid="autocomplete-element"] Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/InteractiveMessage/InteractiveMessage.test.tsx:366:11
src/containers/InteractiveMessage/InteractiveMessage.test.tsx > translates the template > it shows error if clicked on translation without filling details: src/containers/InteractiveMessage/InteractiveMessage.test.tsx#L399
TestingLibraryElementError: Unable to find an element with the text: Add a new Interactive message. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/InteractiveMessage/InteractiveMessage.test.tsx:399:11
src/containers/InteractiveMessage/InteractiveMessage.test.tsx > translates the template > it translates a new template: src/containers/InteractiveMessage/InteractiveMessage.test.tsx#L419
TestingLibraryElementError: Unable to find an element with the text: Add a new Interactive message. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/InteractiveMessage/InteractiveMessage.test.tsx:419:11
src/containers/InteractiveMessage/InteractiveMessage.test.tsx > translates the template > it translates an already exisiting template: src/containers/InteractiveMessage/InteractiveMessage.test.tsx#L454
TestingLibraryElementError: Unable to find an element with the text: Edit Interactive message. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/InteractiveMessage/InteractiveMessage.test.tsx:454:11
src/containers/InteractiveMessage/InteractiveMessage.test.tsx > translates the template > it shows error on translating an already exisiting template: src/containers/InteractiveMessage/InteractiveMessage.test.tsx#L476
TestingLibraryElementError: Unable to find an element with the text: Edit Interactive message. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/InteractiveMessage/InteractiveMessage.test.tsx:476:11
CI
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
CI
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/