Skip to content

Merge pull request #41 from 392-f24/ci-integration #2

Merge pull request #41 from 392-f24/ci-integration

Merge pull request #41 from 392-f24/ci-integration #2

Triggered via push November 6, 2024 21:37
Status Failure
Total duration 24s
Artifacts

main.yml

on: push
Build and unit test
16s
Build and unit test
Cypress test
0s
Cypress test
Firebase deploy
0s
Firebase deploy
Fit to window
Zoom out
Zoom in

Annotations

4 errors
Unhandled error: src/utilities/firebase.js#L4
FirebaseError: Firebase: Error (auth/operation-not-supported-in-this-environment). ❯ createErrorInternal node_modules/@firebase/auth/src/core/util/assert.ts:152:38 ❯ _createError node_modules/@firebase/auth/src/core/util/assert.ts:83:10 ❯ node_modules/@firebase/auth/src/platform_node/index.ts:74:29 ❯ ModuleJob.run node:internal/modules/esm/module_job:268:25 ❯ onImport.tracePromise.__proto__ node:internal/modules/esm/loader:543:26 ❯ VitestExecutor.interopedImport node_modules/vite-node/dist/client.mjs:421:28 ❯ VitestExecutor.directRequest node_modules/vite-node/dist/client.mjs:280:24 ❯ VitestExecutor.cachedRequest node_modules/vite-node/dist/client.mjs:206:14 ❯ VitestExecutor.dependencyRequest node_modules/vite-node/dist/client.mjs:259:12 ❯ src/utilities/firebase.js:4:31 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'auth/operation-not-supported-in-this-environment', customData: {} } This error originated in "src/App.test.jsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "src/App.test.jsx". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
src/App.test.jsx > counter tests > Counter should be 0 at the start: src/App.test.jsx#L9
TestingLibraryElementError: Unable to find an element with the text: count is: 0. 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> <div class="App" > <div class="sign-in-page" > <div class="sign-in" > <div class="house" > <i class="bi bi-house-door" /> </div> <p class="title" > Good Neighbor </p> <button class="green-custom-button btn btn-primary" type="button" > Sign in </button> </div> </div> </div> </div> </body> ❯ Object.getElementError node_modules/@testing-library/dom/dist/config.js:37:19 ❯ node_modules/@testing-library/dom/dist/query-helpers.js:76:38 ❯ node_modules/@testing-library/dom/dist/query-helpers.js:52:17 ❯ node_modules/@testing-library/dom/dist/query-helpers.js:95:19 ❯ src/App.test.jsx:9:19
src/App.test.jsx > counter tests > Counter should increment by one when clicked: src/App.test.jsx#L16
TestingLibraryElementError: Unable to find an element with the text: count is: 1. 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> <div class="App" > <div class="sign-in-page" > <div class="sign-in" > <div class="house" > <i class="bi bi-house-door" /> </div> <p class="title" > Good Neighbor </p> <button class="green-custom-button btn btn-primary" type="button" > Sign in </button> </div> </div> </div> </div> </body> ❯ Object.getElementError node_modules/@testing-library/dom/dist/config.js:37:19 ❯ node_modules/@testing-library/dom/dist/query-helpers.js:76:38 ❯ node_modules/@testing-library/dom/dist/query-helpers.js:52:17 ❯ node_modules/@testing-library/dom/dist/query-helpers.js:95:19 ❯ src/App.test.jsx:16:25
Build and unit test
Process completed with exit code 1.