Argument "using" fails to work

**Version of Nightwatch:**

1.3.6

**Problem:**

Argument "using" fails to work.

**How to simulate:**

Run the following test that passes:

```javascript
module.exports = {

    before: (browser) => {
        browser
            .init();        
    },    

    'Go To Google': (browser) => {
        browser          
            .waitForElementPresent('.gLFyf.gsfi');             
    }, 

    after: (browser) => {
        browser
            .end();
    }
};
```

Now run this one that fails:

```javascript
module.exports = {

    before: (browser) => {
        browser
            .init();        
    },    

    'Go To Google': (browser) => {
        browser          
            .waitForElementPresent('css selector', '.gLFyf.gsfi');             
    }, 

    after: (browser) => {
        browser
            .end();
    }
};
```

It gives this error:

```
✖ .gLFyf.gsfi - expected "found" but got: "not found" (5177ms)
    at Object.Go To Google (/home/pavel/testing/nightwatch_example/tests/visit.js:10:14)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) 


FAILED: 1 assertions failed (5.181s)
_________________________________________________

TEST FAILURE:  1 assertions failed, 0 passed (7.703s)

 ✖ visit
 – Go To Google (5.181s)
   .gLFyf.gsfi - expected "found" but got: "not found" (5177ms)
       at Object.Go To Google (/home/pavel/testing/nightwatch_example/tests/visit.js:10:14)
       at processTicksAndRejections (internal/process/task_queues.js:97:5)
```

But the first argument is one of [these](https://www.w3.org/TR/webdriver/#locator-strategies), which is where you refer to in the [documentation](https://nightwatchjs.org/api/waitForElementPresent.html), and you even mention in some other places like [here](https://nightwatchjs.org/api/waitForElementVisible.html) (Usage section).

**Scope:**

It fails with other API commands (`.waitForElementVisible()` and more), it also fails when using xpath like in this example:

```javascript
module.exports = {

    before: (browser) => {
        browser
            .init();        
    }, 
    
    'Go To Google': (browser) => {
        browser       
            .waitForElementPresent('xpath', '//input[@class="gLFyf gsfi"]');             
    }, 

    after: (browser) => {
        browser
            .end();
    }
};
```

but when used like this, it passes:

```javascript
module.exports = {

    before: (browser) => {
        browser
            .init();        
    }, 
    
    'Go To Google': (browser) => {
        browser       
            .useXpath()
            .waitForElementPresent('//input[@class="gLFyf gsfi"]');             
    }, 

    after: (browser) => {
        browser
            .end();
    }
};
```

I suspect it'd fail with other locator strategies mentioned in the first param in commands, but I didn't try more than css and xpath.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.