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

The "reporter" option from the configuration file will be ignored. #4234

Closed
h-vardhan opened this issue Sep 4, 2019 · 2 comments
Closed
Assignees
Labels
AREA: server FREQUENCY: level 1 STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: configuration storage TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@h-vardhan
Copy link

What is your Test Scenario?

I am running a simple test to check if the html body is present. With that, I am using a reporter in .testcaferc.json

What is the Current behavior?

The test runs successfully but I get this message on console :
The "reporter" option from the configuration file will be ignored.

What is the Expected behaviour?

The .testcaferc.json file shall find the reporter and save report accordingly.

What is your web application and your TestCafe test code?

.testcaferc.json part

{
"reporter": [
    {
      "name": "spec"
    },
    {
      "name": "cucumber-json",
      "output": "mycooltest7-2019-9-4-15-59-46-report.json"
    }
  ]
}

cucumber-json is installed in the version 3.0.1 but this issue is anyway independent of which reporter I am using.
Same error happens with this configuration of reporter

{
"reporter": [
    {
      "name": "spec"
    }
  ]
}

Your website URL (or attach your complete example):

Your complete test code (or attach your test files):
 
Your complete configuration file (if any):
{
  "browsers": "chrome:headless",
  "skipJsErrors": true,
  "selectorTimeout": 10000,
  "pageLoadTimeout": 10000,
  "speed": 1,
  "reporter": [
    {
      "name": "spec"
    },
    {
      "name": "cucumber-json",
      "output": "mycooltest7-2019-9-4-15-59-46-report.json"
    }
  ],
  "takeScreenshotsOnFails": true,
  "videoPath": "videos",
  "videoOptions": {
    "singleFile": false,
    "failedOnly": true,
    "pathPattern": "${FILE_INDEX}.mp4"
  },
  "screenshotPath": "screenshots",
  "screenshotPathPattern": "${FILE_INDEX}.png",
  "concurrency": 1,
  "quarantineMode": true,
}
Your complete test report:
The "reporter" option from the configuration file will be ignored.
 Running tests in:
 - Chrome 76.0.3809 / Mac OS X 10.13.6
Screenshots:

Steps to Reproduce:

  1. Go to my website ...
  2. Execute this command...
  3. See the error...

Your Environment details:

  • testcafe version: 1.4.3
  • node.js version: 12.6.0
  • command-line arguments: testcafe test.js
  • browser name and version: Chrome 76.0.3809
  • platform and version: Mac OS X 10.13.6
  • other:
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Sep 4, 2019
@alexey-lin alexey-lin self-assigned this Sep 4, 2019
@alexey-lin
Copy link
Contributor

Hi @h-vardhan,
 
Thank you for contacting us. We've reproduced the problem on our side. We'll look into it.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Sep 4, 2019
@alexey-lin alexey-lin added AREA: server SYSTEM: configuration storage TYPE: bug The described behavior is considered as wrong (bug). labels Sep 4, 2019
@alexey-lin alexey-lin assigned miherlosev and unassigned alexey-lin Sep 4, 2019
@AndreyBelym AndreyBelym modified the milestones: Planned, Sprint #41 Sep 9, 2019
@lock
Copy link

lock bot commented Sep 20, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Sep 20, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Sep 20, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
…n file will be ignored. "' (close DevExpress#4234) (DevExpress#4242)

* initial

* tmp

* improove test

* debug

* debug 2

* revert debug code
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: server FREQUENCY: level 1 STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: configuration storage TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

4 participants