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

Process hangs if tests were run in nightmare #1493

Closed
AlexanderMoskovkin opened this issue May 23, 2017 · 5 comments
Closed

Process hangs if tests were run in nightmare #1493

AlexanderMoskovkin opened this issue May 23, 2017 · 5 comments
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@AlexanderMoskovkin
Copy link
Contributor

(created from the stackoverflow question)

The process doesn't exit after tests run if testcafe-browser-provider-nightmare is used.
We should check where we should fix it in testcafe or in the provider.

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

createTestCafe('localhost', 1337, 1338)
.then(tc => {
    testcafe     = tc;
    runner = testcafe.createRunner();

    return runner
        .src(['offerRefresh.js'])
        .browsers(['nightmare'])
        .screenshots('./screenshots', true)
        .run();
})
.then(failedCount => {
    console.log('Tests failed: ' + failedCount);
    testcafe.close();
});

The console remains like this:

Tests failed: 0

And never closes the process.

Specify your

  • testcafe version: 0.15.0
@AlexanderMoskovkin AlexanderMoskovkin added the TYPE: bug The described behavior is considered as wrong (bug). label May 23, 2017
@inikulin
Copy link
Contributor

I bet it's a nightmare process that is never terminated and blocking node from exit.

@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #8 milestone Jun 9, 2017
@AndreyBelym
Copy link
Contributor

@AndreyBelym
Copy link
Contributor

Fixed in [email protected].

@AlexanderMoskovkin
Copy link
Contributor Author

AlexanderMoskovkin commented Sep 12, 2017

@AndreyBelym, nice job!

@lock
Copy link

lock bot commented Mar 28, 2019

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 Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 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. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

3 participants