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
Bug 1878873 : cypress-cucumber-automation-framework #6776
Bug 1878873 : cypress-cucumber-automation-framework #6776
Conversation
/assign @dtaylor113 |
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.
Hi @makambalaji, thanks for breaking down this PR to a smaller size. I think we still need to work on using common helper methods, and if they do not meet some needs, enahnce the already existing ones. -thanks
Also please link a Bugzilla or JIRA story to this PR which will keep track of removing all the css selectors. - thanks
frontend/packages/dev-console/integration-tests/support/pages/add-flow/add-page.ts
Show resolved
Hide resolved
frontend/packages/dev-console/integration-tests/support/commands/app.ts
Outdated
Show resolved
Hide resolved
frontend/packages/dev-console/integration-tests/support/commands/app.ts
Outdated
Show resolved
Hide resolved
frontend/packages/dev-console/integration-tests/support/commands/app.ts
Outdated
Show resolved
Hide resolved
frontend/packages/dev-console/integration-tests/support/pages/app.ts
Outdated
Show resolved
Hide resolved
frontend/packages/dev-console/integration-tests/support/pages/app.ts
Outdated
Show resolved
Hide resolved
frontend/packages/dev-console/integration-tests/support/pages/app.ts
Outdated
Show resolved
Hide resolved
frontend/packages/dev-console/integration-tests/reporter-config.json
Outdated
Show resolved
Hide resolved
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 thanks!
/approve |
/lgtm |
"test-cypress-devconsole": "cd packages/dev-console/integration-tests && ../../../node_modules/.bin/cypress open --env openshift=true", | ||
"test-cypress-devconsole-headless": "cd packages/dev-console/integration-tests && node --max-old-space-size=4096 ../../../node_modules/.bin/cypress run --env openshift=true --browser ${BRIDGE_E2E_BROWSER_NAME:=chrome} --headless --spec \"features/project-creation.feature\";", |
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.
Will these tests run as part of CI? Do they run if I use yarn run test-cypress-headless
?
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.
Yes, test-cypress-headless
is now:
"test-cypress-headless": "yarn run test-cypress-console-headless && yarn run test-cypress-devconsole-headless",
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.
But how will this scale if every package adds a test?
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.
@makambalaji i thought you weren't planning to run all the dev-console tests on CI because you said it took hours to run.
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.
@spadgett - From dev-console side, Will select the test scenarios for execution based on the tag names mentioned in cypress.json
@christianvogt - In CI, will run only smoke tests, now the execution time is also reduced from 2.5 hr to 1 hr.
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.
This pr doesn't add 1hr of tests. I'd like to get the smoke tests down below 1hr down before adding all those tests.
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.
But how will this scale if every package adds a test?
@spadgett I was envisioning teams adding to test-cypress-headless
in the same manor. Teams need to cd
to their cypress dir, so it seems to be the correct method.
@makambalaji frontend failed...
|
@andrewballantyne : updated the eslintrc file |
Re-adding the lgtm based on the linter change (last commit). /lgtm |
/approve |
As per the openshift-ci-robot comments, assigning pr to Sam for approval |
/retest |
1 similar comment
/retest |
/approve But you need to run prettier :) |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
/hold so openshift-bot doesn't continually try to Failure seems to be this:
|
@makambalaji please update yarn.lock: |
Hi @makambalaji, |
/retest |
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
/hold cancel |
/hold until #7053 merges! Apologies @makambalaji, there was a CI regression when we added OLM Cyrpess tests and we were blocking the Once #7053 merges you will need to uncomment this, and resolve merge conflicts in |
test-prow-e2e.sh
Outdated
@@ -17,7 +17,7 @@ trap copyArtifacts EXIT | |||
|
|||
# don't log kubeadmin-password | |||
set +x | |||
BRIDGE_KUBEADMIN_PASSWORD="$(cat "${INSTALLER_DIR}/auth/kubeadmin-password")" | |||
BRIDGE_KUBEADMIN_PASSWORD="$(cat "${KUBEADMIN_PASSWORD_FILE:-${INSTALLER_DIR}/auth/kubeadmin-password}")" |
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.
Why is this change neccesary? Where is KUBEADMIN_PASSWORD_FILE
set?
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.
Somehow it got added, Now I removed it, Could you please review it now
updated Read-Me document, package.json and Report file name updated test attributes in add page.ts and added data test atttibutes in dev code for monitoring page commented a11y vaidations and raised the defects for the same Updated .git-ignore with package-lock.json because it is not listed in our dependencies
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 Thanks @makambalaji !
/hold cancel |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewballantyne, christianvogt, dtaylor113, makambalaji, sanketpathak, spadgett The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
As per the comments mentioned in PR : #6618, splitting PR into small pr's
jira Id : ODC-4926
Tracking the addition of data-test attributes to the dev-console code using JIRA id : ODC-4937