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

"describe does not expect any arguments" received when incorrect number of arguments requested #6838

Closed
fabiancook opened this issue Aug 14, 2018 · 2 comments · Fixed by #6843

Comments

@fabiancook
Copy link

🐛 Bug Report

When using the incorrect amount of arguments for describe I receive an error that doesn't match whats actually happening

To Reproduce

Steps to reproduce the behavior:

// This will throw "describe does not expect any arguments"
describe.each([
  ['key', 'value']
])('%s', (key, value, extra) => {
   test('key doesn't equal value', () => expect(key).not.toEqual(value));
});

Expected behavior

I would expect the error message to say something along the lines of describe expects <n> arguments to be utilised or similar

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: macOS High Sierra 10.13.4
    CPU: x64 Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz
  Binaries:
    Node: 8.10.0 - /usr/local/bin/node
    Yarn: 1.9.4 - /usr/local/bin/yarn
    npm: 5.6.0 - /usr/local/bin/npm
  npmPackages:
    jest: ^23.5.0 => 23.5.0 
@thymikee
Copy link
Collaborator

cc @mattphillips

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants