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

[Bug]: Using done with it.concurrent(...) causes TypeError #12085

Closed
rickerp opened this issue Nov 25, 2021 · 3 comments
Closed

[Bug]: Using done with it.concurrent(...) causes TypeError #12085

rickerp opened this issue Nov 25, 2021 · 3 comments

Comments

@rickerp
Copy link

rickerp commented Nov 25, 2021

Version

27.0.2

Steps to reproduce

describe("some describe description", () => {
  it.concurrent("some it concurrent description", (done) => {
    done()
  }
})

Expected behavior

It should not throw an error

Actual behavior

TypeError: done is not a function

Additional context

This is related with #10529 , but since I'm not using async functions directly or returning a promise directly (I am using a synchronous function in it.concurrent) I decided to open this issue.

Environment

Windows WSL
System:
    OS: Linux 5.10 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor  
Binaries:
    Node: 14.18.1 - ~/.nvm/versions/node/v14.18.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v14.18.1/bin/yarn
    npm: 6.14.15 - ~/.nvm/versions/node/v14.18.1/bin/npm  
npmPackages:
    jest: ^27.3.0 => 27.3.1
@rickerp rickerp changed the title [Bug]: it.concurrent() with done cause TypeError [Bug]: Using done with it.concurrent(...) causes TypeError Nov 25, 2021
@github-actions
Copy link

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the Stale label Nov 25, 2022
@github-actions
Copy link

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 25, 2022
@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 Jan 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant