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

Selector is expected to be initialized with a function, CSS selector #4400

Closed
Meemaw opened this issue Oct 18, 2019 · 2 comments
Closed

Selector is expected to be initialized with a function, CSS selector #4400

Meemaw opened this issue Oct 18, 2019 · 2 comments
Labels
STATE: Need clarification An issue lacks information for further research.

Comments

@Meemaw
Copy link

Meemaw commented Oct 18, 2019

After upgrading to testcafe v1.6.0 it seems that @testing-library/testcafe selectors started failing:

import { getByPlaceholderText } from '@testing-library/testcafe';

  const searchInput = getByPlaceholderText( 'Type...');
  await t
    .expect(searchInput.exists)
    .ok('Search input exists')
    .typeText(searchInput, 'randomText');

Throws:
Screen Shot 2019-10-18 at 11 57 02 AM

Error points to the .typeText line.

Your Environment details:

  • testcafe version: 1.6.0
  • node.js version: v8.16.0
  • browser name and version: HeadlessChrome 68.0.3440
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Oct 18, 2019
@Dmitry-Ostashev
Copy link
Contributor

This behavior is most likely caused by the @testing-library/testcafe library. I suggest you create an issue in this repository: https://github.com/testing-library/testcafe-testing-library.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Oct 18, 2019
@Dmitry-Ostashev Dmitry-Ostashev removed their assignment Oct 18, 2019
@miherlosev miherlosev added the STATE: Need clarification An issue lacks information for further research. label Oct 18, 2019
@no-response
Copy link

no-response bot commented Oct 28, 2019

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Oct 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Need clarification An issue lacks information for further research.
Projects
None yet
Development

No branches or pull requests

3 participants