manikanth

Issues in including Selenium script for WAS

Discussion created by manikanth on Oct 31, 2019
Latest reply on Nov 5, 2019 by Chetan Joshi
Branched from an earlier discussion

Help me to sort out the below problem....

 

  

When we are performing a was scan using selenium script which is created using qualys recorder when we run a test case manually it is working then when we perform authentication scan or vulnerability scan in the 150100 Selenium Diagnostics it is showing the below error and also the authentication status is displaying as "Not Used" also the same authentication error ( authentication status is displaying as "Not Used) is displaying when we perform standard and custom methods.

  

 

  


Executing: |open | https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx| |
Executing: |click | id=idxxxx | |
Executing: |sendKeys | id=idxxxx
Executing: |waitForElementPresent | id=loginxx| |
Executing: |click | id=loginxx| |
Executing: |waitForElementPresent | id=password | |
currentTest.recordFailure: Timed out after 60000ms
Executing: |waitForVisible | id=password | |
currentTest.recordFailure: Timed out after 60000ms
Executing: |click | id=password | |
currentTest.recordFailure: Element id=password not found

  

 

  

the error it is displaying currentTest.recordFailure: Element id=password not found

  

also authentication Not used

Outcomes