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

ERROR TypeError: Cannot read property 'test' of undefined in version 1.8.0 #4661

Closed
devmondo opened this issue Jan 19, 2020 · 2 comments · Fixed by DevExpress/testcafe-browser-tools#191
Labels
AREA: server !IMPORTANT! 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

@devmondo
Copy link

What is your Test Scenario?

simple one from the docs
https://devexpress.github.io/testcafe/documentation/getting-started/

What is the Current behavior?

just upgraded to 1.8.0 and wither you use CLI or programmatic interface we get this error:
ERROR TypeError: Cannot read property 'test' of undefined
it does not happen with 1.7.xxx

What is the Expected behavior?

run as usual

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 configuration file (if any):

Your complete test report:
ERROR TypeError: Cannot read property 'test' of undefined
    at C:\projects\test\testcafe-simple-test\node_modules\testcafe-browser-tools\src\api\get-installations.js:61:24
    at Array.some (<anonymous>)
    at addInstallation (C:\projects\test\testcafe-simple-test\node_modules\testcafe-browser-tools\src\api\get-installations.js:58:30)
    at async Promise.all (index 3)
    at searchInRegistry (C:\projects\test\testcafe-simple-test\node_modules\testcafe-browser-tools\src\api\get-installations.js:97:5)
    at findWindowsBrowsers (C:\projects\test\testcafe-simple-test\node_modules\testcafe-browser-tools\src\api\get-installations.js:104:39)
    at findBrowsers (C:\projects\test\testcafe-simple-test\node_modules\testcafe-browser-tools\src\api\get-installations.js:170:16)
    at Object.default_1 [as default] (C:\projects\test\testcafe-simple-test\node_modules\testcafe-browser-tools\src\api\get-installations.js:223:30)
    at Object.default_1 [as getBrowserInfo] (C:\projects\test\testcafe-simple-test\node_modules\testcafe-browser-tools\src\api\get-browser-info.js:24:27)
    at BrowserProviderPluginHost.isValidBrowserName (C:\projects\test\testcafe-simple-test\node_modules\testcafe\src\browser\provider\built-in\dedicated\base.js:25:29)
    at BrowserProvider.isValidBrowserName (C:\projects\test\testcafe-simple-test\node_modules\testcafe\src\browser\provider\index.ts:279:16)
    at Object.getBrowserInfo (C:\projects\test\testcafe-simple-test\node_modules\testcafe\src\browser\provider\pool.js:108:14)
    at async Promise.all (index 0)
    at Bootstrapper._getBrowserInfo (C:\projects\test\testcafe-simple-test\node_modules\testcafe\src\runner\bootstrapper.ts:206:29)
    at Bootstrapper.createRunnableConfiguration (C:\projects\test\testcafe-simple-test\node_modules\testcafe\src\runner\bootstrapper.ts:421:29)

Screenshots:

Steps to Reproduce:

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

Your Environment details:

  • testcafe version: 1.8.0
  • node.js version: 12.6.0
  • command-line arguments:
  • browser name and version:
  • platform and version: Window x64 bit
  • 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 Jan 19, 2020
@AndreyBelym AndreyBelym added !IMPORTANT! AREA: server SYSTEM: browser natives TYPE: bug The described behavior is considered as wrong (bug). labels Jan 20, 2020
@AndreyBelym AndreyBelym added this to the Sprint #49 milestone Jan 20, 2020
@AndreyBelym
Copy link
Contributor

Thank you for your report, I've reproduced the issue.

@lock
Copy link

lock bot commented Jan 31, 2020

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 Jan 31, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Jan 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: server !IMPORTANT! 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