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

Fix test script, add Mocha result checks to internal Cypress te… #7110

Merged
merged 12 commits into from
Apr 23, 2020

Conversation

flotwig
Copy link
Contributor

@flotwig flotwig commented Apr 22, 2020

Closes #7052

Additional details

  • fixes cypress.js test script so it will exit with a non-zero exit code if an error occurs
  • adds cypress-multi-reporters to desktop-gui and driver and reporter and ui-components so they output a junit xml report
  • adds verify-mocha-results test stage to those cypress tests

@cypress-bot
Copy link
Contributor

cypress-bot bot commented Apr 22, 2020

Thanks for the contribution! Below are some guidelines Cypress uses when doing PR reviews.

  • Please write [WIP] in the title of your Pull Request if your PR is not ready for review - someone will review your PR as soon as the [WIP] is removed.
  • Please familiarize yourself with the PR Review Checklist and feel free to make updates on your PR based on these guidelines.

PR Review Checklist

If any of the following requirements can't be met, leave a comment in the review selecting 'Request changes', otherwise 'Approve'.

User Experience

  • The feature/bugfix is self-documenting from within the product.
  • The change provides the end user with a way to fix their problem (no dead ends).

Functionality

  • The code works and performs its intended function with the correct logic.
  • Performance has been factored in (for example, the code cleans up after itself to not cause memory leaks).
  • The code guards against edge cases and invalid input and has tests to cover it.

Maintainability

  • The code is readable (too many nested 'if's are a bad sign).
  • Names used for variables, methods, etc, clearly describe their function.
  • The code is easy to understood and there are relevant comments explaining.
  • New algorithms are documented in the code with link(s) to external docs (flowcharts, w3c, chrome, firefox).
  • There are comments containing link(s) to the addressed issue (in tests and code).

Quality

  • The change does not reimplement code.
  • There's not a module from the ecosystem that should be used instead.
  • There is no redundant or duplicate code.
  • There are no irrelevant comments left in the code.
  • Tests are testing the code’s intended functionality in the best way possible.

Internal

  • The original issue has been tagged with a release in ZenHub.

@cypress
Copy link

cypress bot commented Apr 22, 2020



Test summary

7182 0 98 0


Run details

Project cypress
Status Passed
Commit 05e5927
Started Apr 23, 2020 2:43 PM
Ended Apr 23, 2020 2:49 PM
Duration 05:44 💡
OS Linux Debian - 10.1
Browser Multiple

View run in Cypress Dashboard ➡️


This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

@flotwig flotwig marked this pull request as ready for review April 23, 2020 15:33
command: |
CYPRESS_KONFIG_ENV=production \
CYPRESS_RECORD_KEY=$PACKAGES_RECORD_KEY \
yarn cypress:run --record --parallel --group 5x-driver-<< parameters.browser >> --browser << parameters.browser >>
Copy link
Contributor

Choose a reason for hiding this comment

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

i feel like this one would be a good Circle command to factor out


# "driver-integration-tests-electron":
# <<: *defaults
# parallelism: 5
# steps:
# - attach_workspace:
Copy link
Contributor

Choose a reason for hiding this comment

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

I like how you removed commented out code too :) and inserted commented out NEW code

Copy link
Contributor Author

Choose a reason for hiding this comment

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

gotta keep those comments up to date!

@@ -619,7 +601,9 @@ jobs:
command: |
CYPRESS_KONFIG_ENV=production \
CYPRESS_RECORD_KEY=$PACKAGES_RECORD_KEY \
yarn lerna exec --scope @packages/desktop-gui "yarn cypress:run --record --parallel --group 2x-desktop-gui"
yarn cypress:run --record --parallel --group 2x-desktop-gui
Copy link
Contributor

Choose a reason for hiding this comment

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

sweet change

@@ -2,5 +2,9 @@
"baseUrl": "http://localhost:5005",
"projectId": "ypt4pf",
"viewportWidth": 800,
"viewportHeight": 850
"viewportHeight": 850,
"reporter": "../../node_modules/cypress-multi-reporters/index.js",
Copy link
Contributor

Choose a reason for hiding this comment

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

are you pointing at the cypress-multi-reporters at the root, then why add them to each package?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it makes intuitive sense for them to be installed per-package, but yarn hoists them, and cypress won't load it by name if it's hoisted outside the current directory (#4536). so it was really just a choice, it could also be installed in the root package

Copy link
Contributor

@bahmutov bahmutov left a comment

Choose a reason for hiding this comment

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

I like it, just had a question about cypress-multi-reporter in each package

@flotwig flotwig changed the title Fix test script, add Mocha result checks to internal Cypress tests Fix test script, add Mocha result checks to internal Cypress te… Apr 23, 2020
@flotwig flotwig merged commit c80e482 into develop Apr 23, 2020
@flotwig flotwig deleted the issue-7052-2 branch January 24, 2022 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CircleCI exits as passing when Cypress tests have failed in our development
2 participants