Codekru

Welcome back In the previous article, you learned to ask whether an element is visible, enabled, or selected. Those checks now become part of a real task: filling a form. A form collects information and choices through controls such as inputs, checkboxes, radio buttons, and dropdowns. Selenium handles each control according to the way it […]

Welcome back In the previous article, you learned how to click, type, clear, read, and assert. You also skipped the disabled button on TestKru because finding a button does not prove that it can be used. Today you will inspect a control before acting on it. Selenium element states answer three practical questions: Question WebElement

Welcome back You have finished Module 2. You can now choose a stable locator, use a visual relationship when you need one, and check whether a search matched once. Finding a control is only the first half of a test. A locator that returns the last-name field does not, by itself, prove that a user

Welcome back In the previous lesson, you learned how to choose a stable locator. You looked for a unique clue, then proved that your locator matched exactly one element. That rule still guides this lesson. Today you will add one new tool. Sometimes a control has no useful unique id, name, or class. However, it

Welcome back In the previous article, you learned relative XPath, functions such as contains() and starts-with(), and axes that walk from one cell to its neighbors. Combined with the CSS lesson before that, you now have the syntax to find almost anything on a page. Syntax is not the hard part anymore. The hard part

Welcome back In the previous article, you learned Selenium’s locator menu and a simple order of preference: unique id first, then a clear CSS selector when id is missing, then XPath when relationships demand it. This lesson zooms into CSS. You will learn the selector patterns you will reuse on almost every real page: id,

Welcome back In the previous article, you learned browser-level commands: open a URL, read the title, move through history, resize the window, and work with tabs. Those commands talk to the browser as a whole. They never need a locator, because they are not looking for one field or button. Almost every real test still

Welcome back In the previous article, you built a local lab and ran one TestNG test. Chrome opened, TestKru loaded, an assertion passed, and quit() closed the browser. That test worked, but some of it may still feel unclear. Which line started the browser? Which object typed the text? Why did the browser close at

Install Java, IntelliJ, and Maven, add Selenium 4 and TestNG, then run your first Chrome WebDriver test on TestKru.