e2e test: 01-settings/appearance.cy.js is failing
igarashitm opened this issue · 1 comments
igarashitm commented
Describe the Bug
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Cypress: 12.17.2 │
│ Browser: Electron 106 (headless) │
│ Node Version: v16.17.0 (/home/tomo/.nvm/versions/node/v16.17.0/bin/node) │
│ Specs: 19 found (01-settings/about.cy.js, 01-settings/appearance.cy.js, 01-settings/s │
│ ettings.cy.js, 02-editing_properties/editing.cy.js, 03-step_integration/step_i │
│ ntegration.cy.js, 04-source_code/source_code.cy.js, 06-undo_redo_actions/undo_ │
│ redo_actions.cy.js, 05-...) │
│ Searched: cypress/e2e/**/*.{js,jsx,ts,tsx} │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
────────────────────────────────────────────────────────────────────────────────────────────────────
Running: 01-settings/about.cy.js (1 of 19)
Settings: About
✓ Close and reopen about modal (6207ms)
1) Check that the about modal contains the correct information
1 passing (17s)
1 failing
1) Settings: About
Check that the about modal contains the correct information:
Timed out retrying after 8000ms
+ expected - actual
-'1.2.0-SNAPSHOT'
+'<!DOCTYPE html>\n<html lang="en-US">\n\n<head>\n <meta charset="utf-8">\n <title>Kaoto</title>\n <meta id="appName" name="application-name" content="Kaoto">\n <meta name="viewport" content="width=device-width, initial-scale=1.0">\n <link rel="icon" type="image/svg+xml" href="./favicon.svg" />\n<link rel="icon" href="favicon.svg"><script defer src="main.js"></script></head>\n\n<body>\n<noscript>Enabling JavaScript is required to run this app.</noscript>\n<div id="app"></div>\n</body>\n\n</html>\n'
at Context.eval (webpack:///./cypress/e2e/01-settings/about.cy.js:41:70)
Steps to Reproduce the Bug or Issue
- cd packages/kaoto-ui
- yarn e2e:headless
Screenshots or Videos
No response
Platform
- OS: [e.g. macOS, Windows, Linux]
- Browser: [e.g. Chrome, Safari, Firefox]
- Version: [e.g. 0.30.0]
lordrip commented
It turns out that this situation was due to the .env
file missing. It would be interesting to check the possibility to generate this file after issuing yarn install
in a post-install hook.