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 jenkins -> cypress parameter #192

TheBestPessimist opened this issue Jul 2, 2019 · 0 comments


1 participant
Copy link

commented Jul 2, 2019

This issue is related to

  • (e.g. a metasfresh-me03 issue)

Test shall include:

  • Customer Fixtures to use: (if needed)
  • What to test
  • Expectation for the test to be successful

Todo for developer (besides coding)

  • Always make sure the issue is in the correct project lane
  • run your test in jenkins e2e on a vanilla db
  • jenkins console URL / cypress dashboard URL to the successful test run (alternatively screenshot)
  • get it integrated into master
    • (pull request URL)

All Flags are ticked? Congratulations, you have delivered!


14:12:15  CYPRESS_BROWSER=electron
14:12:15  CYPRESS_SPEC=**/integration/sales/**
14:12:15  ⚠ Warning: It looks like you're passing --spec a space-separated list of files:
14:12:15  "cypress/integration/sales/credit_memo_for_sales_invoice.js cypress/integration/sales/credit_memo_price_difference_for_sales_invoice.js"
14:12:15  This will work, but it's not recommended.
14:12:15  The most common cause of this warning is using an unescaped glob pattern. If you are
14:12:15  trying to pass a glob pattern, escape it using quotes:
14:12:15    cypress run --spec "**/*.spec.js"
14:12:15  If you are trying to pass multiple spec filenames, separate them by commas instead:
14:12:15    cypress run --spec spec1,spec2,spec3

the spec i passed as parameter in jenkins is **/integration/sales/**.
i think jenkins should be fixed to passed the specs to cypress as "**/integration/sales/**"

@TheBestPessimist TheBestPessimist added this to To do in e2e via automation Jul 2, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.