Repository navigation
Description
What is your Scenario?
i'm testing a Vue3 application. Without nativeAutomation everything runs fine (the tests i mean)
If i turn on NativeAutomation, the tests just stops, or hangs or just doesn't do anything.
There are no errors, no warnings in the output of testcafe, nor in the console of the browser. It just 'stops'. it seems like the expect doesn't signal to the test that it is finished.
As you can see in below example, i get the console.logs a and b, but never c. the browser just sits there. Also no timeout errors. just ...nothing...
I cannot create a sample repo as it is internal app. but i would like to have hints or tips on what i can turn on to get more info or debug info? I tried debugMode, and it stops at the first expect, upon resuming it has the same behaviour: it just stops
What is the Current behavior?
test run just hangs
What is the Expected behavior?
run to the finish
What is your public website URL? (or attach your complete example)
internal app.
What is your TestCafe test code?
import RequestTravellerInfo from '../pageModels/RequestTravellerInfo';
fixture('Request traveller info page')
.page(RequestTravellerInfo.pageURL)
test('The request-traveller-info page should show the correct title', async (testController) => {
console.log('do i get here?','a');//yes
await testController
.expect(RequestTravellerInfo.title.innerText)
.contains('Warp tickets');
console.log('do i get here?','b');//yes
await testController
.expect(RequestTravellerInfo.title.innerText)
.contains('Warp tickets');
});
test('The user should be able to fill in the inputfield firstname', async (testController) => {
console.log('do i get here?','c');//NO!!
await testController
.typeText(RequestTravellerInfo.firstNameInput, 'Spock')
.expect(RequestTravellerInfo.firstNameInput.value).eql('Spock');
});
Your complete configuration file
{
"browsers": [
"chrome"
],
"src": "./tests/functional/**/*.cspec.js",
"hostname": "localhost",
"reporter": [
{
"name": "spec"
},
{
"name": "html",
"output": "./tests/functional/reports/html/index.html"
},
{
"name": "xunit",
"output": "./tests/functional/reports/report.xml"
}
],
"screenshots": {
"takeOnFails": true,
"path": "./tests/screenshots",
"fullPage": true,
"pathPattern": "${FIXTURE}/${TEST}/test-${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}.png"
},
"pageLoadTimeout": 10000,
"clientScripts": [
{
"module": "axe-core/axe.min.js"
}
],
"debugMode": true,
"nativeAutomation": true
}
Your complete test report
no report, because the tests doesn't conclude.
Screenshots
No response
Steps to Reproduce
TestCafe version
2.5.0
Node.js version
16.18.1
Command-line arguments
testcafe './tests/functional/fixtures/RequestTravellerInfo.cspec.js'
Browser name(s) and version(s)
chrome 112
Platform(s) and version(s)
macOS 13.3.1
Other
No response
Activity
github-actions commentedon Apr 25, 2023
Thank you for submitting this issue. We would love to assist you and diagnose it. However, we need a simple sample that we can easily run on our side in order to replicate the issue and research its cause. Without a sample, we are not able to figure out what's going on and why this issue occurs. Refer to this article to create the best example: How To: Create a Minimal Working Example When You Submit an Issue. We look forward to your response.
jurgensweere commentedon Apr 26, 2023
Here is a sample repository to replicate the issue:
https://github.com/jurgensweere/hello-world
It is a vuejs application generated with the vue-cli, added testcafe, enabled nativeAutomation and added 5 tests. When running in Node v18.16.0 (or v16.19.0) it will run 1 (or 2) tests successfully but never reaches any additional tests.
You can replicate by cloning the repository and then:
npm installnpm run serve-testAlexKamaev commentedon Apr 27, 2023
Thank you for your cooperation. I managed to reproduce the issue. We'll research it.
mikkel-ol commentedon May 2, 2023
+1
fix: fixed hanging in NA if url has hash (#7698)
github-actions commentedon May 26, 2023
Release v2.6.1-rc.1 addresses this.
awacode21 commentedon Nov 14, 2024
i am running in the same issue. what fixes it?
PavelMor25 commentedon Nov 18, 2024
Hello @awacode21,
Could you please create a separate ticket based on this template and share more details? Specifically: