Skip to content
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

Removing Protractor annotations test from e2e, crud, and all test suites due to flakyness #7322

Conversation

dtaylor113
Copy link
Contributor

@dtaylor113 dtaylor113 commented Nov 24, 2020

We are currently porting over annotation tests to Cypress: https://issues.redhat.com/browse/CONSOLE-2478

@@ -59,7 +59,6 @@ const testSuites = {
'tests/crud.scenario.ts',
'tests/secrets.scenario.ts',
'tests/filter.scenario.ts',
'tests/modal-annotations.scenario.ts',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should leave the scenario and use xdescribe so we see they're disabled in the log and JUnit report.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The downside to that is beforeAll and afterAll will still run...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The downside to that is beforeAll and afterAll will still run...

i should say, base.scenario.ts including Create a test namespace will still run.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that only runs once for the entire e2e suite?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it runs for each suite. but it's fine. dave's gonna remove these soon anyhow.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, and I just checked a few annotation failures, they seem to happen during the actual test, not in before hooks:

26) Modal Annotations
   ✔ Delete Annotation
   ✔ Add numeric Annotation from grid
   ✔ Add alphanumeric Annotation from object detail
   ✔ Add Annotation without value
   ✖ Add annotation wihout key (1 failure)
   • Update Annotation from value to empty value: CONSOLE-394
   • Update Annotation from empty value to value
   • Cancel add Annotation

@dtaylor113 dtaylor113 force-pushed the protractor-disable-annotations-tests branch from a1c09a1 to 3f64b91 Compare November 24, 2020 20:57
@dtaylor113 dtaylor113 force-pushed the protractor-disable-annotations-tests branch from 3f64b91 to 811433d Compare November 24, 2020 21:00
Copy link
Member

@spadgett spadgett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 24, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dtaylor113, 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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 24, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@dtaylor113
Copy link
Contributor Author

/hold
Until "quay.io has a service degratation incident." is resolved.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 25, 2020
@openshift openshift deleted a comment from openshift-bot Nov 25, 2020
@openshift openshift deleted a comment from openshift-bot Nov 25, 2020
@dtaylor113
Copy link
Contributor Author

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 30, 2020
@dtaylor113
Copy link
Contributor Author

/retest

@openshift openshift deleted a comment from openshift-bot Nov 30, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

3 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@dtaylor113
Copy link
Contributor Author

/retest

@openshift-merge-robot openshift-merge-robot merged commit 8adb81d into openshift:master Dec 1, 2020
@spadgett spadgett added this to the v4.7 milestone Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants