Many website developers will setup buttons or other elements within the site to be "disabled" until a certain action occurs. When using Test Studio to test this, it is sometimes necessary to create a special verification that confirms that the button (in this example) is visible but disabled (not clickable/usable). You can similarly verify that the disabled attribute no longer exists, indicating the button is clickable/usable.
For example, when you have a disabled or not disabled element on a page that needs to be verified/waited for, or you have another attribute within the markup of an element you wish to search for (you can modify this process for your own needs).
1. Start recording.
2. 2.Navigate to the page/step with the disabled element you'd like to verify.
- Enable hover over highlighting.
- Hover the mouse over the applicable element
- Choose Build Step
- In the Build Step menu click Attributes
- Choose the proper attribute and the its state.
3. Click Add Step.
4. A new Verify rule will be created within the Test at the location you specified. You can right click this step to Change Role and Set as Wait, if desired.
There are two ways to do that:
1. 1.Write the Find Logic yourself in code. Use this approach if you are using Telerik Testing Framework only. You can insert this logic in the same coded step that does the disabled verification.
Element e = Find.ByExpression("id=myInput");
2. Add the element to your Project Elements, then reference it from that source. Use this approach if you are using Test Studio Standalone version or the Visual Studio plugin.
HtmlInputText e = Pages.TryitEditorV14.FrameView.LnameText;
3. Once you have your Element e, here is the verification in code: