bug
Looks like a regression of this issue: https://github.com/DevExpress/testcafe/issues/2132
In v0.22.0 - after test completes, Chrome process remains open (in dock)
In v0.20.5 - after test completes, Chrome browser closes
Run test using Chrome:
npx testcafe chrome test.js
Tested page URL:
https://devexpress.github.io/testcafe/example
Test code
// From your github page: https://github.com/DevExpress/testcafe
import { Selector } from 'testcafe'; // first import testcafe selectors
fixture `Getting Started`// declare the fixture
.page `https://devexpress.github.io/testcafe/example`; // specify the start page
//then create a test and place your code there
test('My first test', async t => {
await t
.typeText('#developer-name', 'John Smith')
.click('#submit-button')
// Use the assertion to check if the actual header text is equal to the expected one
.expect(Selector('#article-header').innerText).eql('Thank you, John Smith!');
});
Hi @jantonypdx, I guess it's a regression of https://github.com/DevExpress/testcafe/issues/2226. Please read my comment for more details. Could you please run ps -ef >ps-ef.log and ps aux >ps-aux.log after running TestCafe, and post the ps-ef.log and ps-aux.log files?
Here you go:
ps-ef.log
ps-aux.log
Hi @jantonypdx, sorry for the late response. Judging by the differences in the log files, it's really the regressed #2226. I think we have to get rid of the ps-node module, because it works unreliably on macOS systems.
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.
Most helpful comment
Hi @jantonypdx, sorry for the late response. Judging by the differences in the log files, it's really the regressed #2226. I think we have to get rid of the
ps-nodemodule, because it works unreliably on macOS systems.