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

Different errors for missing browsers #3534

Closed
arubtsov opened this issue Mar 6, 2019 · 1 comment · Fixed by #3540
Closed

Different errors for missing browsers #3534

arubtsov opened this issue Mar 6, 2019 · 1 comment · Fixed by #3540
Labels
AREA: server STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: browser natives TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@arubtsov
Copy link
Contributor

arubtsov commented Mar 6, 2019

What is your Test Scenario?

Run a tests specifying not installed browser's alias.

What is the Current behavior?

I get different errors for different browsers:

  1. chrome\firefox:
Error: Was unable to open the browser "%browserName%" due to error.

Error: Unable to run the browser. The browser path or command template is not specified.
    at checkBrowserPath$ (D:\Projects\github-studio\node_modules\testcafe-browser-tools\lib\api\open.js:47:23)
    at tryCatch (D:\Projects\github-studio\node_modules\testcafe-browser-tools\node_modules\babel-runtime\regenerator\runtime.js:72:40)
    at Generator.invoke [as _invoke] (D:\Projects\github-studio\node_modules\testcafe-browser-tools\node_modules\babel-runtime\regenerator\runtime.js:334:22)
    at Generator.prototype.(anonymous function) [as next] (D:\Projects\github-studio\node_modules\testcafe-browser-tools\node_modules\babel-runtime\regenerator\runtime.js:105:21)
    at tryCatch (D:\Projects\github-studio\node_modules\testcafe-browser-tools\node_modules\babel-runtime\regenerator\runtime.js:72:40)
    at invoke (D:\Projects\github-studio\node_modules\testcafe-browser-tools\node_modules\babel-runtime\regenerator\runtime.js:146:20)
    at D:\Projects\github-studio\node_modules\testcafe-browser-tools\node_modules\babel-runtime\regenerator\runtime.js:191:11
    at new Promise (<anonymous>)
    at new F (D:\Projects\github-studio\node_modules\testcafe-browser-tools\node_modules\core-js\library\modules\$.export.js:30:36)
    at callInvokeWithMethodAndArg (D:\Projects\github-studio\node_modules\testcafe-browser-tools\node_modules\babel-runtime\regenerator\runtime.js:190:16)
  1. opera\safari:
Error: Unable to find the browser. "%browserName%" is not a browser alias or path to an executable file.

What is the Expected behavior?

Consistent errors.

What is your web application and your TestCafe test code?

Your website URL (or attach your complete example):

Your complete test code (or attach your test files):
 
Your complete test report:

Screenshots:

Steps to Reproduce:

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

Your Environment details:

  • testcafe version: 1.0.2-alpha.1
  • node.js version: v10.15.0
  • command-line arguments:
  • browser name and version:
  • platform and version: Windows 10
  • other:
@AndreyBelym AndreyBelym added TYPE: bug The described behavior is considered as wrong (bug). SYSTEM: browser natives AREA: server labels Mar 6, 2019
@AndreyBelym AndreyBelym added this to the Sprint #29 milestone Mar 6, 2019
@AndreyBelym AndreyBelym modified the milestones: Sprint #29, Sprint #30 Mar 18, 2019
AndreyBelym added a commit that referenced this issue Mar 20, 2019
…3540)

* Fix error messages when can't find firefox & chrome

* Fix tests on Node 6
@lock
Copy link

lock bot commented Mar 30, 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 Mar 30, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 30, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
…s#3534) (DevExpress#3540)

* Fix error messages when can't find firefox & chrome

* Fix tests on Node 6
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: server STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: browser natives TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants