镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

testcafe just stops/hangs with nativeAutomation true #7652

Closed

Description

@stefanlivens

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

  1. added
    TYPE: bugThe described behavior is considered as wrong (bug).
    on Apr 21, 2023
  2. github-actions commented on Apr 25, 2023

    @github-actions

    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.

  3. jurgensweere commented on Apr 26, 2023

    @jurgensweere

    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 install
    npm run serve-test

  4. AlexKamaev commented on Apr 27, 2023

    @AlexKamaev
    Contributor

    Thank you for your cooperation. I managed to reproduce the issue. We'll research it.

  5. mikkel-ol commented on May 2, 2023

    @mikkel-ol

    +1

  6. removed
    STATE: Need responseAn issue that requires a response or attention from the team.
    on May 2, 2023
  7. self-assigned this
    on May 3, 2023
  8. added a commit that references this issue on May 16, 2023
    9808995
  9. github-actions commented on May 26, 2023

    @github-actions

    Release v2.6.1-rc.1 addresses this.

  10. awacode21 commented on Nov 14, 2024

    @awacode21

    i am running in the same issue. what fixes it?

  11. PavelMor25 commented on Nov 18, 2024

    @PavelMor25
    Contributor

    Hello @awacode21,

    Could you please create a separate ticket based on this template and share more details? Specifically:

    • Minimal working example
    • Configuration
    • Browser
    • OS version
    • Exact Node.js version
    • Any additional information that might help us reproduce the issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions