-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Enterprise Search] Set up basic scaffolding for Cypress tests in Kibana #108560
Conversation
- Required if we're going to have several different Cypress suites (one for each plugin/product essentially) in order for global cy.() commands and it()/describe() to register as expected @see https://docs.cypress.io/guides/tooling/typescript-support#Clashing-types-with-Jest
NOTE: Unlike ent-search, shared/ will *not* have its own set of tests - rather, shared/cypress is a resource/set of helpers for other test suites to extend/import/etc.
- For happy path testing, we _likely_ shouldn't need more than these tests going forward - If we ever want to add an error connecting test however, this is likely where it should go (or alternatively, use Kibana's FTR with Enterprise Search host set but not spun up)
- placeholder/hello world test only
- placeholder/hello world test only
…nst Kibana functional server
3f5685b
to
a9d8447
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code is good and I couldn't get the files to appear again.
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but one nit
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
…ana (elastic#108560) * Set up tsconfigs - Required if we're going to have several different Cypress suites (one for each plugin/product essentially) in order for global cy.() commands and it()/describe() to register as expected @see https://docs.cypress.io/guides/tooling/typescript-support#Clashing-types-with-Jest * Set up shared commands and routes NOTE: Unlike ent-search, shared/ will *not* have its own set of tests - rather, shared/cypress is a resource/set of helpers for other test suites to extend/import/etc. * Create basic Enterprise Search Overview E2E tests - For happy path testing, we _likely_ shouldn't need more than these tests going forward - If we ever want to add an error connecting test however, this is likely where it should go (or alternatively, use Kibana's FTR with Enterprise Search host set but not spun up) * Set up App Search Cypress test scaffolding - placeholder/hello world test only * Set up Workplace Search Cypress test scaffolding - placeholder/hello world test only * Add helper script and update README * Add config setup & documentation for potentially running Cypress against Kibana functional server * PR feedback: Fix typescript project names Co-authored-by: Kibana Machine <[email protected]>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
…ana (#108560) (#108779) * Set up tsconfigs - Required if we're going to have several different Cypress suites (one for each plugin/product essentially) in order for global cy.() commands and it()/describe() to register as expected @see https://docs.cypress.io/guides/tooling/typescript-support#Clashing-types-with-Jest * Set up shared commands and routes NOTE: Unlike ent-search, shared/ will *not* have its own set of tests - rather, shared/cypress is a resource/set of helpers for other test suites to extend/import/etc. * Create basic Enterprise Search Overview E2E tests - For happy path testing, we _likely_ shouldn't need more than these tests going forward - If we ever want to add an error connecting test however, this is likely where it should go (or alternatively, use Kibana's FTR with Enterprise Search host set but not spun up) * Set up App Search Cypress test scaffolding - placeholder/hello world test only * Set up Workplace Search Cypress test scaffolding - placeholder/hello world test only * Add helper script and update README * Add config setup & documentation for potentially running Cypress against Kibana functional server * PR feedback: Fix typescript project names Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Constance <[email protected]>
Fix
This PR is #108309 but with Typescript configuration causing issues in master fixed 🤞
The issue appears to be that I hadn't specified an
outDir
config to a gitignored folder such astarget
, and as such compiled.d.ts
and.map
files were getting generated and then tracked in git on everyyarn kbn bootstrap
.I've run
yarn kbn clean
andyarn kbn bootstrap
locally and all my type checks are still working for me, but I'll also be asking other fellow Enterprise Search devs to test this locally and confirm that their bootstrap on this branch works without unexpected issues.Original PR description
Summary
Why is Enterprise Search choosing to write E2E tests in Cypress over Kibana's FTR?
What this PR does:
.js
filessh cypress.sh run overview
from the enterprise_search plugin folder and have all tests passWhat this PR does NOT do:
As always, I recommend following along by commit.
Screencaps
cypress.mp4
QA
kibana.dev.yml
, setcsp.strict: false
andcsp.warnLegacyBrowsers: false
--no-base-path
and on localhost:5601sh cypress.sh run overview
passessh cypress.sh run as
passessh cypress.sh run ws
passesChecklist