Dynamic Programming Articles - Page 4 of 14

TestNG supports multi-invocation of a test method, i.e., a @Test method can be invoked multiple times sequentially or in parallel. If we want to run single @Test 10 times at a single thread, then invocationCount can be used.To invoke a method multiple times, the keyword invocationCount = is required. For example −@Test(invocationCount = 10)In this example, the @Test method will execute for 10 times each on a single thread.In this article, we will illustrate how to get the current invocation count.Approach/Algorithm to solve this problemStep 1 − Create a TestNG class, NewTestngClass.Step 2 − Write two @Test methods in ... Read More

TestNG supports a lot of assertions. It has the org.testng.Assert class, which extends the Java object class java.lang.object. Whenever there is a failure, the user wants to get a customized failure message so that the root-cause analysis could be easy. TestNG supports assertion with customized failure message. However, message is completely optional.The syntax is −Assert.(expected, actual, message)If the user doesn't provide a message, TestNG prints a default error message; but if the user sets a message, then TestNG throws the error along with the customized message set by the user.In this article, we will see how to set a custom ... Read More

TestNG supports native dependency injection. It allows to declare additional parameters in methods. At runtime, TestNG automatically fills these parameters with the correct values. Here is a set of native dependencies in TestNG:ITestContextXmlTestMethodITestResultThese dependencies help to retrieve the Test method name. A Test method name can be retrieved before or after the execution of the test.If the user wants to get the name of a Test method prior to its execution, @BeforeMethod can be useful to retrieve it.If the user wants to know which Test method is just executed, @AfterMethod can be used.The actual code can be written in either ... Read More

TestNG supports native dependency injection. It allows to declare additional parameters in methods. At runtime, TestNG automatically fills these parameters with the correct values. Following is a set of native dependencies in TestNG −ITestContextXmlTestMethodITestResultThese dependencies help to retrieve the description of Test method, if written. A Test method name can be retrieved before or after the execution of the test.If the user wants to get the description of a test method prior to its execution, then @BeforeMethod can be useful to retrieve it.If the user wants to know the description of a Test method after it is executed, then @AfterMethod ... Read More

testng.xml has a format as where we define what all test classes should be executed. Users can mention n number of classes in testing.xml that require executing. In this article, we are going to discuss how to execute more than one class using a single testing.xml.Here, we will have two classes with multiple test methods, and we will see how testng.xml is configured to run both the classes - NewTestngClass and OrderofTestExecutionInTestNG.Approach/Algorithm to solve this problemSetp 1 − Create two TestNG classes - NewTestngClass and OrderofTestExecutionInTestNG.Setp 2 − Write two different @Test method in both the classes - NewTestngClass ... Read More

We can obtain the tagname of the parent element in Selenium webdriver. First of all, we need to identify the child element with help of any of the locators like id, class, name, xpath, or CSS. Then we have to identify the parent with the findElement(By.xpath()) method.We can identify the parent from the child, by localizing it with the child and then passing (parent::*) as a parameter to the findElement(By.xpath()). Next, to get the tagname of the parent, we have to use the getTagName() method.Syntaxchild.findElement(By.xpath("parent::*"));Let us identify tagname of the parent of child element li in the below html code ... Read More

We can obtain the page title using Selenium webdriver. The method getTitle() is used to obtain the present page title and then we can get the result in the console.Syntaxt = driver.getTitle();Let us find the title of the current page. We shall get About Careers at Tutorials Point – Tutorialspoint as output.ExampleCode Implementation.import org.openqa.selenium.By; import org.openqa.selenium.WebDriver; import org.openqa.selenium.WebElement; import org.openqa.selenium.chrome.ChromeDriver; import java.util.concurrent.TimeUnit; public class PageTitle{    public static void main(String[] args) {       System.setProperty("webdriver.chrome.driver",       "C:\Users\ghs6kor\Desktop\Java\chromedriver.exe");       //implicit wait       driver.manage().timeouts().implicitlyWait(5, TimeUnit.SECONDS);       WebDriver driver = new ChromeDriver(); ... Read More

We can upload files using Selenium Webdriver. This is achieved by the sendKeys method. We have to first identify the element which performs the file selection by mentioning the file path [to be uploaded].This is only applied to an element having a type attribute set to file as a value along with the element tag name as input. The below html code shows the element with type = file value set.ExampleCode Implementation.import org.openqa.selenium.By; import org.openqa.selenium.WebDriver; import org.openqa.selenium.WebElement; import org.openqa.selenium.chrome.ChromeDriver; import java.util.concurrent.TimeUnit; public class WndsFileUpl{    public static void main(String[] args) {       System.setProperty("webdriver.chrome.driver",       "C:\Users\ghs6kor\Desktop\Java\chromedriver.exe");   ... Read More

We can work with Selenium webdriver with Java Quickstart template. This can be done by following the below steps −Step1− Click on the File menu in Eclipse. Then select the option New. Next click on Other.Step2− Click on Maven Project from the Maven folder. Then click on Next.Step3− Proceed with the further steps.Step4− Select maven-archetype-quickstart template. Then click on Next.Step5− Add GroupId as Selenium, Artifact Id as Automation-Selenium, and proceed.Step6− A project should get created with an archetype project structure. The Selenium-related scripts should be written within the src/test/java folder.

We can run tests using a test runner file for Cucumber. The test runner file should contain the path of the feature file and step definition file that we want to execute.Code Implementation of the Feature fileFeature − Login ModuleScenario − Welcome Page Login verificationGiven User is on Welcome PageThen Welcome page should be displayedExampleCode Implementation of step definition filepackage stepDefinations; import io.cucumber.java.en.Given; import io.cucumber.java.en.Then; public class stepDefination {    @Given("^User is on Welcome Page$")    public void user_on_welcome_page() {       System.out.println("User on welcome page");    }    @Then("^Welcome page should be displayed$")    public void verify_user_on_welcome_page() {   ... Read More