Custom step interigate DOM?

Hello David,

There are methods that I believe can help you achieve the exact scenario that you want to automate. You can use the Find.AllByTagName<>() or Find.AllByExpression<>() to get a collection of all elements that match the criteria.

Once you have this collection of elements, you can iterate it and execute custom logic against each of the elements. In your case, you need to type some text. This can be done with the following code example, which simulates the real user behavior and ensure that the focus is on the target element before typing.

Actions.SetText(yourElement, "");        // clear the current text        yourElement.ScrollToVisible(ArtOfTest.WebAii.Core.ScrollToVisibleType.ElementCenterAtWindowCenter);
ActiveBrowser.Window.SetFocus();
yourElement.Focus();
yourElement.MouseClick();
Manager.Desktop.KeyBoard.TypeText("text", 50, 100, true); //enter the text with desktop keyboard actions

Please explore the above suggestions and code sample and test them on your end. I remain available to advise you further or answer any follow up questions that you might have.

Regards,
Plamen Mitrev
Progress Telerik

Is it possible to find all controls on a page that have a  specific class name like this control?

<input name="ctl00$ContentPlaceHolder1$txt_arrival" type="text" id="ContentPlaceHolder1_txt_arrival" style="width:75px;" class="hasDatepicker">

So this code finds the button as I see it highlighted but when it clicks it the web app blows up

            Element btn = Find.ByAttributes("value=Continue");
            
            if (btn != null)
            {
                System.Threading.Thread.Sleep(1000); 
                Actions.Click(btn);
            }

when I look at how test studio does it by looking at the test step generated code it does this and works

            // Click 'ContentPlaceHolder1BtnContinueSubmit'
            Pages.SynchronizedPredeployment7.ContentPlaceHolder1BtnContinueSubmit.Click(false);

but I need to find the button and click. Any ideas?

ok we are having an issue with the find.Allbyattributes looking for controls. It works fine on a page that has the following controls:

<input name="ctl00$ContentPlaceHolder1$txt_arrival" type="text" id="ContentPlaceHolder1_txt_arrival" style="width:75px;" class="hasDatepicker">

<input type="submit" name="ctl00$ContentPlaceHolder1$btn_continue" value="Continue" onclick="javascript:WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions(&quot;ctl00$ContentPlaceHolder1$btn_continue&quot;, &quot;&quot;, true, &quot;&quot;, &quot;&quot;, false, false))" id="ContentPlaceHolder1_btn_continue" style="cursor: pointer;">

*** This is the code for the first page that works:

// Find all elements with class=hasDatepicker and src has a type of text
            IList<Element> allItems = Find.AllByAttributes("class=hasDatepicker", "type=text");
            
            foreach (Element item in allItems)
            {
                Actions.SetText(item,"13/13/1313");
                System.Threading.Thread.Sleep(1000); 
            }       
            
           
            HtmlInputControl btn = Find.ByAttributes<HtmlInputControl>("value=Continue");
            System.Threading.Thread.Sleep(3000);    
            
            if (btn != null)
            {
                btn.Focus();
                btn.MouseClick();
            }

*** The 2nd page that the find does not work on has these controls:

<input name="ctl00$ContentPlaceHolder1$txtPOPStart" type="text" maxlength="10" id="ContentPlaceHolder1_txtPOPStart" tabindex="3" class="hasDatepicker">

<input type="submit" name="ctl00$ContentPlaceHolder1$btnSearchContracts" value="Search for Contracts" onclick="javascript:WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions(&quot;ctl00$ContentPlaceHolder1$btnSearchContracts&quot;, &quot;&quot;, true, &quot;&quot;, &quot;&quot;, false, false))" id="ContentPlaceHolder1_btnSearchContracts" tabindex="13" style="cursor: pointer;">

*** This is the test code for the 2nd page that does not find either of the controls

IList<Element> allItems = Find.AllByAttributes("class=hasDatepicker", "type=text");
            
            foreach (Element item in allItems)
            {
                Actions.SetText(item,"13/13/1313");
                System.Threading.Thread.Sleep(1000); 
            }       
            
            MessageBox.Show(window, "# Dates found: " + allItems.Count());
           
            HtmlInputControl btn = Find.ByAttributes<HtmlInputControl>("value=Search for Contracts", "type=submit");

** We even have searched for the exact control names but it finds nothing. HELP!!!!!

Hello David,

Thank you for sharing a sample from your application and the code that you have tested on your end. I used that to host a local page that has two inputs and two buttons, same as yours, and prepared a sample web test with a coded step that enters text in both inputs and clicks the buttons. Please find more details below and the sample test attached to this reply.

Since you already know the type of elements you are getting from the Find.AllByAttributes() method -> HtmlInputText, I would advise you to specify their type directly there. This makes it easier to work with those elements using the Telerik Testing Framework. 

I adjusted your code to set the text exactly at the target element of each iteration. That way the text is set exactly for the specified element and you don't need to take care of which element is on focus at the moment of execution. I also made some small changes to your code that clicks the buttons to make sure that they are visible on the screen, before they are clicked.

You can record actions or verifications with the Test Studio standalone product and convert the steps into coded steps. That way you can explore what series of methods is used in a single step. Please keep in mind that Test Studio stores the target elements in the Elements Explorer and references them in the coded step from the Pages object. If you are using only coded steps, I advise you to use a suitable Find.By...() method.

Please explore the sample page and attached web test with coded step on your end and use similar logic to automate your test scenario. If you encounter any troubles, please share the DOM tree of the tested application and your current code, as well as the results from the test execution.

Thank you for your cooperation in this discussion.

Regards,
Plamen Mitrev
Progress Telerik

Hello David,

I am happy to hear that refreshing the DOM tree improved the execution of your test scenario. I assume that some actions before the coded step change the content of the page or redirect it to a different page.

You can consider the suggestions from my previous reply, which are general guidelines on how to use the Find.By... methods to make your tests more stable. Let me know if you experience any issues or need further assistance.

Thank you for providing feedback about your adopted solution.

Regards,
Plamen Mitrev
Progress Telerik