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

No xml in case of a test clicking on an unpresent nested element in parallel with any other test #3163

Closed
sarahRaafat15 opened this issue Apr 20, 2022 · 6 comments · Fixed by #3178 or #3213
Assignees

Comments

@sarahRaafat15
Copy link

Describe the bug

In case of trying to click on an unpresent nested element and in case of running such test with another one in parallel, no xml gets generated and browserstack session would be unmarked instead of normal failure.
Captureb

Sample test

nightwatch_test.js

module.exports = {
  props: {},
  sections: {
    firstSection: {
      selector: "div",
      elements: {
        navItem: "li.nav"
      }
    }
  }

parallelTest1.js

//sample test
it("sample step", function(browser) {
      var nightwatch_test = browser.page.nightwatch_test();
      browser.url("https://nightwatchjs.org/")
      nightwatch_test.section.firstSection.click({
        selector: "@navItem",
      })
    })

parallelTest2.js

// Please add the sample test here

it("parallel step", function(browser) {
      browser.url("https://google.com/")
    })

**Run with command**
$ nightwatch test/sampleTest.js --your-other-arguments-here

Your Environment

Executable Version
nightwatch --version 2.0.6
npm --version 8.3.1
node --version v16.14.0

| Browser driver | Version |
| chromedriver | 98.0.0 |

| OS | Version |
| Windows | 10 |

@gravityvi
Copy link
Member

@sarahRaafat15, Thanks for sharing the issue. We will look into it.

@gravityvi gravityvi self-assigned this Apr 27, 2022
@sarahRaafat15
Copy link
Author

This is happening with every base Element Command not just clicks

@mostmentor
Copy link

I'm still seeing this issue with nightwatch 2.1.6
image

@gravityvi
Copy link
Member

@mostmentor Can you provide the sample tests that are not working for you? It would help to detect the issue and fix it.

@mostmentor
Copy link

I tried the above tests attached in the ticket parallel parallelTest1.js & parallelTest2.js

@gravityvi
Copy link
Member

@mostmentor @sarahRaafat15 I will look into it again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants