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

Asynchronous tests running #1460

Closed
gerardus1995 opened this issue May 3, 2017 · 2 comments
Closed

Asynchronous tests running #1460

gerardus1995 opened this issue May 3, 2017 · 2 comments
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. STATE: Duplicate An issues has been already reported in the other thread. TYPE: enhancement The accepted proposal for future implementation.

Comments

@gerardus1995
Copy link

Are you requesting a feature or reporting a bug?

Feature

What is the current behavior?

testcafe.createRunner() executes every fixture one after the other.

What is the expected behavior?

Is there any way to execute all at the same time (asynchronously). Like opening 4 consoles and executing 4 tests at same time (with nightmare headless browser).

How would you reproduce the current behavior (if this is a bug)?

Provide the test code and the tested page URL (if applicable)

Tested page URL:

Test code

Specify your

  • operating system: Mac OSX
  • testcafe version:
  • node.js version:
@AlexanderMoskovkin AlexanderMoskovkin added TYPE: proposal STATE: Duplicate An issues has been already reported in the other thread. labels May 3, 2017
@AlexanderMoskovkin
Copy link
Contributor

AlexanderMoskovkin commented May 3, 2017

Hi,

Thanks for the proposal. We have this feature in our planned milestone but now we have no estimated date for it. You can vote for the feature by adding your 👍 there: #1165

@AndreyBelym AndreyBelym added TYPE: enhancement The accepted proposal for future implementation. and removed TYPE: proposal labels Feb 6, 2019
@lock
Copy link

lock bot commented Mar 27, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs or feature requests. For TestCafe API, usage and configuration inquiries, we recommend asking them on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 27, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. STATE: Duplicate An issues has been already reported in the other thread. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

No branches or pull requests

3 participants