qase-tms / qase-cypress

Qase TMS Cypress Reporter
Apache License 2.0
9 stars 1 forks source link

"cypress-qase-reporter" reporter not found Reporter not found! on version 1.1.2 #4

Closed estefafdez closed 3 years ago

estefafdez commented 3 years ago

Hello.

I have an open-source license to use the API and publish the test on Qase.

I have the project already setup and the test run created but every time that I run the tests I got the following error:

"cypress-qase-reporter" reporter not found Reporter not found! cypress-qase-reporter

You can see the code here: https://github.com/estefafdez/cypress-template/tree/dev-api-tests

Could you let me know what am I doing wrong? The results are not updated.

Thanks!

zeburek commented 3 years ago

I will check what's wrong and will return here

estefafdez commented 3 years ago

I've also tried to install the dev dependencies:

npm install cypress-qase-reporter --save-dev

same result.

zeburek commented 3 years ago

@estefafdez could you please check latest version? v1.2.0

estefafdez commented 3 years ago

Hello @zeburek , same problem here, I can't publish the result.

Is there a way for the plugin to create a new test run automatically on Qase and then publish the results instead of creating one manually and set the runId parameter on the project?

zeburek commented 3 years ago

Use cypressQaseReporterReporterOptions instead of cypress-qase-reporterOptions

That's the problem. In demo project there is a correct example

estefafdez commented 3 years ago

@zeburek same result with and without runId:

    "cypressQaseReporterReporterOptions": {
        "apiToken": "xxx",
        "projectCode": "CYEX",
        "logging": true
    }

You can download the project from my repo and check the code yourself, it's on the dev-api-testbranch.

Thanks!

zeburek commented 3 years ago

@estefafdez Just checked your dev-api-test branch locally: image image

PS: Don't forget to NOT push sensitive information to git repo

estefafdez commented 3 years ago

@zeburek could you tell me what command did you run? I can't reproduce that :(

about the API key, it was there just for testing and for trying to resolve this problem, I will generate a new one once is fixed and I will save it as a private key on the repo!

zeburek commented 3 years ago

@zeburek could you tell me what command did you run? I can't reproduce that :(

npm run test

zeburek commented 3 years ago

Have you run npm install after your latest changes? may be it is related

estefafdez commented 3 years ago

I will try later today.

Just to confirm, if I want a new test run to be created without adding the testRun ID on the project, how can I do it? Thanks!

zeburek commented 3 years ago

To do it now - you just shouldn’t provide testrun ID anywhere - by doing this script will try to create testrun by itself

estefafdez commented 3 years ago

Ok great, working now :)

one last question before closing the issue. Is there a way to close the TestRun after is finished?

Thanks! :)

estefafdez commented 3 years ago

Also, a new test run is created on each spec, could it be possible to create one testrun with all the tests instead of a testrun per spec?

For example: https://github.com/estefafdez/cypress-template/runs/1878060734?check_suite_focus=true

zeburek commented 3 years ago
  1. No, actually it is not implemented, you can file a ticket for this.
  2. Now it is made that way. I know that it is not good and I will take a look how to overcome this. But If you want to parallel Cypress you will create separate runs, as a result - you will face the same issue
estefafdez commented 3 years ago

Nice, thanks @zeburek. I will create two tickets for both and you will keep me posted :) thanks for the help!