We have a dialog, where we use table viewer and in one of the columns, we used a Boolean data which are shown in the form of radio buttons. While running an UFT based automation suite which clicks the radio button and also encounters a confirmation dialog and clicks some other radio button again. In that above process we encounter the issue which is not possible to encounter while testing manually.
I would like to know what the issue might be.
Let me know if there is a way to fix it.
The situation is that I have multiple checkboxes in the dropdown list.
So when selecting all of them by WebDriverWait(driver, 5).until(ec.visibility_of_element_located([
By.XPATH......))] and then click, sometimes the last checkbox is not being saved until I do another action after that.
Is there any way in Selenium to do "Force check" or some other way to forcefully check the checkboxes?
In Playwright Framework there is element().check(Force = force_check) option for such situations. So I want to understand what we can do with Selenium?
Thanks in advance.
We have one website (third party software), that I am only having issues with. I am getting the following error:
java.net.ConnectException: Connection refused: connect
The only thing different with this button than other buttons in this software/site and others is this form action.
<form action="https://test.xxxxxxxxxx.org/customer/account/createpost/" method="post" id="form-validate" class="scaffold-form" enctype="multipart/form-data">
It clocks and waits and returns the above message....but the form has been submitted and continues to the next screen, but Selenium loses it. I have no idea if that form action has anything to do with it, but anything outside of it, will not lose control.
Any way to work around this? Anyone else run into this issue?
It is because of the form action. I had to change it from a "Click" action to a submit. I found it from this link
Selenium Webdriver submit() vs click()
Sorry..I have been doing this lately. I ask a question and it prompts me to look up the question in a different way that garners different result, and that is what happened this time.
My test automation uses Selenium for UI interactions and fiddlercore api to capture the events generated by UI. Situation I am facing right now is fiddlercore is failing to capture event that is caused by click on a button. I have tried following ways:
builder.MoveToElement(searchButton).Click(searchButton).Build().Perform();
searchButton.SendKeys(Keys.Enter);
searchButton.Click();
None of these could generate that event. When I click them actually I am able to see that specific event. Are these all soft clicks and could that be the reason of not able to get that event?
I am having trouble getting Selenium IDE to click the Submit button on one of my webforms after having selenium open and fill out the form. I am using the clickAndWait command and identifying the button by its ID:
<td>clickAndWait</td>
<td>id=ctl00_ContentPlaceHolder1_OSVFHResults_btSave</td>
<td></td>
Interestingly, if I write a script that simply opens the form and clicks the submit button without filling it out, I am not having any problems. My problem is coming specifically after I've asked Selenium to fill out the form. Additionally, if I try to manually click the submit button, it doesn't work if the Selenium script to fill out the form was run before my manual input. If I manually open and fill out the form, I have no problems clicking submit, and Selenium works for all of the other form's submit buttons on the site. Anyone have any ideas?
Instead of filling form with type command you can try typeKeys one. It simulates keystroke events on the specified element, as though you typed the value key-by-key and probably enable your submit button.
It sounds like some javascript event unrelated to click() (such as mouseover or onkeydown) is attached to one or more of the form fields and is responsible for enabling the submit button.
You'd have to look at which exact events are being fired, either by looking at the source with something like firebug, or by using a javascript debugger. Then modify your Selenium script to make sure the same events get triggered.
After type the values in the form just try "ClickAtandWait" instead of "clickandWait"..i also face the problem once and it gave hands once..
selenium.clickAtandWait("locator", "position");
if you know the exact "position" just put it, otherwise leave it as an empty string.