We have learnt in previous posts regarding establishing relationship between test methods. You can go through them below: Dependency in TestNG – Creating Dependency Among Test Methods – DependsOnMethod Dependency in TestNG – Creating Dependency Among Test Methods – DependsOnGroup Before we learn about types of dependencies in TestNG, lets see one scenario first: If
In previous post, We have learnt to Establish dependency among test methods. In this post, we will see another concept in Dependency called DependsOnGroup. Consider a scenario: You have created automation scripts for Integration testing. We know that in integration testing, data flows from one module to another. You divide your test methods as per group.
We are going to see another important concept or feature provided by TestNG. This feature is called as Dependency. Suppose, we need to post a status on Facebook. Let’s write a Test Case for it: Step 1: Launch browser. Step 2: Launch Facebook url. Step 3: Create an account on Facebook. Step 4: Post a
A Test method is run for all data set provided by a DataProvider method which is by default one after another. Note here that test method is run on data in same sequence in which DataProvider pass it. The reason behind this is that a DataProvider annotated method has an attribute named “parallel” whose default
By default a Test method is executed for all data set returned by DataProvider. The reason behind this is that a DataProvider annotated method has an attribute called “indices” whose default value is set to “all”. You may need to run only specific set of data. Like if DataProvider providing you five set of data
In last post, we have learnt how can we make parameterized DataProvider method in TestNG to provide test data to multiple Test methods from single DataProvider method. Let’s make it more customised. Suppose you need to read data from external file like Excel, properties file etc in a DataProvider method. The name of external file
“DataProvider” is an important feature provided by TestNG to provide required test data to test methods to run on. We have learnt different approaches which we can utilize to get best of DataProvider in previous posts. Let’s learn another way to make more use of DataProvider in TestNG. Suppose we have three Test methods and
Hello, DataProvider is an important functionality provided by TestNG to achieve Data driven testing or providing a set of different dataset to a method to execute on. We have seen DataProvider concept in details in previous posts. DataProvider may become nightmare if number of data (arguments) is more or it keeps changing or you do not
Hello Folks, As part of ongoing series on DataProvider, we will learn “How does Encapsulation ( in OOPS concept) help in a DataProvider method? ” in this post. Encapsulation is an Object Oriented Programming concept which describes binding of related stuffs together under one roof. It makes easier to add , remove and modify members. For
Hello Guys, DataProvider method in TestNG is a way to provide test data to Test annotated methods in a TestNG class. A typical DataProvider method looks like as below:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
// A data provider method with return type as 2D array @DataProvider(name = "DataContainer") public Object[] myDataProvider() { return new Object[][] { { "Mukesh", "Otwani", "Motwani@gmail.com" }, { "Amod", "Mahajan", "Amahajan@hotmail.com" }, { "Animesh", "Prashant", "aprashant@gmail.com" }, { "Ankur", "Singh", "asingh@gmail.com" }, { "Amritansh", "Kumar", "akumar@gmail.com" } }; } |
You can see that return type of above DataProvider method is an Object array. Is it mandatory to have return type as Object only? Answer
