Answers for "Data Driven testing example"

data driven testing

Data-Driven Tests is a procedure when you repeat the same scenario with different input parameters and then verify the result with the given output values.
Test data is always an important part of automated tests. Test data is not just the value or the text in the application, but it's about the whole environment that we are testing.
We usually use hard-coded data in the data that we are editing in our test script, like username password, or URL.
For example, if we have different testing environments with different URLs, we need to add these URLs in one file and read the correct data from the file.
But if we add it and decide in this case, it will be hardcoded, they can't be configurable.
Another example - if we have a registration form and they need to test this form for positive and negative scenarios, we need to prepare different sets of data for this case, to be able to provide the application behavior.

data driven testing

Data-Driven Tests is a procedure when you repeat the same scenario with different input parameters and then verify the result with the given output values.
Test data is always an important part of automated tests. Test data is not just the value or the text in the application, but it's about the whole environment that we are testing.
We usually use hard-coded data in the data that we are editing in our test script, like username password, or URL.
For example, if we have different testing environments with different URLs, we need to add these URLs in one file and read the correct data from the file.
But if we add it and decide in this case, it will be hardcoded, they can't be configurable.
Another example - if we have a registration form and they need to test this form for positive and negative scenarios, we need to prepare different sets of data for this case, to be able to provide the application behavior.

data driven testing in api

If you use JUnit-5 in your framework,
it allows to use @ParameterizedTest annotation
beside @Test annotation. 
There are different way to achieve 
DDT with @ParameterizedTest annotation.
(1-valueSource , 2- csvSource , 3-CsvFileSource)

1. 	@ParameterizedTest
    @ValueSource(ints = {1,2,3,4})
    public void validateRegionNameTest1(int id) {
        given().pathParam("id", id)
                .when().get("/regions/{id}")	==> It will use 1,2,3,4 as 
                id in different runs...
                .prettyPeek()
                .then().assertThat().statusCode(200)
                .and().assertThat().body("region_id", equalTo(id));
    }

2.  @ParameterizedTest
    @CsvSource({
            "1, Europe",
            "2, Americas",
            "3, Asia",
            "4, Middle East and Africa"})
    public void validateRegionNameTest2(int id, String name) {  ==> iterate 
    each data set one by one 
    		given().pathParam("id", id)
                .when().get("/regions/{id}")
                .prettyPeek()
                .then().assertThat().statusCode(200)
                .and().assertThat().body("region_id", equalTo(id))
                .and().assertThat().body("region_name", equalTo(name));
    }

3.  @ParameterizedTest
    @CsvFileSource(resources = "/regions.csv") ==> uses external csv 
    file which is located under resources directory
    public void validateRegionNameTest3(int id, String name) {
        given().pathParam("id", id)
                .when().get("/regions/{id}")
                .prettyPeek()
                .then().assertThat().statusCode(200)
                .and().assertThat().body("region_id", equalTo(id))
                .and().assertThat().body("region_name", equalTo(name));
    }

data driven testing framework

HOW DO YOU IMPLEMENT DATA DRIVEN TESTING IN YOUR FRAMEWORK?
	
	TESTNG:
	1. @DataProvider annotation
	2. Excel file with the help of Apache POI
	3. JSON or CSV file for API testing
	4. Data which comes from Database and stores in collections

	To use the DataProvider feature in the 
    test cases, you have to declare a method
    annotated by @DataProvider and then use 
    the said method in the test method using
    the ‘dataProvider‘ attribute in the @Test annotation.

	CUCUMBER / JUNIT:
	1. Scenario outline
	2. Excel file with the help of Apache POI
	3. JSON or CSV file for API testing
	4. Data which comes from Database and stores in collections
	5. @ParameterizedTest --> If you use JUnit-5
		
	
	Examples for ParameterizedTest:

	@ParameterizedTest
    @ValueSource(ints = {1,2,3,4})  ==>
    it can be ints/strings/booleans/chars (those are keywords)
    public void validateRegionNameTest1(int id) {
     xxxxx
    }

    @ParameterizedTest
    @CsvSource({
            "1, Europe",
            "2, Americas",
            "3, Asia",
            "4, Middle East and Africa"})
    public void validateRegionNameTest2(int id, String name){ 
    xxxx
    }

    @ParameterizedTest
    @CsvFileSource(resources = "/regions.csv")

    @ParameterizedTest(name = "{index} => a={0}, b={1}, sum={2}")
    @MethodSource("sumProvider")
  
    @ParameterizedTest(name = "{index} => pet=''{0}''")
    @EnumSource(value = Pet.class, names = {"CAT"})

    @ParameterizedTest(name = "{index} => a={0}, b={1}, sum={2}")
    @ArgumentsSource(CustomArgumentProvider.class)

data driven testing framework

HOW DO YOU IMPLEMENT DATA DRIVEN TESTING IN YOUR FRAMEWORK?
	
	TESTNG:
	1. @DataProvider annotation
	2. Excel file with the help of Apache POI
	3. JSON or CSV file for API testing
	4. Data which comes from Database and stores in collections

	To use the DataProvider feature in the 
    test cases, you have to declare a method
    annotated by @DataProvider and then use 
    the said method in the test method using
    the ‘dataProvider‘ attribute in the @Test annotation.

	CUCUMBER / JUNIT:
	1. Scenario outline
	2. Excel file with the help of Apache POI
	3. JSON or CSV file for API testing
	4. Data which comes from Database and stores in collections
	5. @ParameterizedTest --> If you use JUnit-5
		
	
	Examples for ParameterizedTest:

	@ParameterizedTest
    @ValueSource(ints = {1,2,3,4})  ==>
    it can be ints/strings/booleans/chars (those are keywords)
    public void validateRegionNameTest1(int id) {
     xxxxx
    }

    @ParameterizedTest
    @CsvSource({
            "1, Europe",
            "2, Americas",
            "3, Asia",
            "4, Middle East and Africa"})
    public void validateRegionNameTest2(int id, String name){ 
    xxxx
    }

    @ParameterizedTest
    @CsvFileSource(resources = "/regions.csv")

    @ParameterizedTest(name = "{index} => a={0}, b={1}, sum={2}")
    @MethodSource("sumProvider")
  
    @ParameterizedTest(name = "{index} => pet=''{0}''")
    @EnumSource(value = Pet.class, names = {"CAT"})

    @ParameterizedTest(name = "{index} => a={0}, b={1}, sum={2}")
    @ArgumentsSource(CustomArgumentProvider.class)

data driven testing in api

If you use JUnit-5 in your framework,
it allows to use @ParameterizedTest annotation
beside @Test annotation. 
There are different way to achieve 
DDT with @ParameterizedTest annotation.
(1-valueSource , 2- csvSource , 3-CsvFileSource)

1. 	@ParameterizedTest
    @ValueSource(ints = {1,2,3,4})
    public void validateRegionNameTest1(int id) {
        given().pathParam("id", id)
                .when().get("/regions/{id}")	==> It will use 1,2,3,4 as 
                id in different runs...
                .prettyPeek()
                .then().assertThat().statusCode(200)
                .and().assertThat().body("region_id", equalTo(id));
    }

2.  @ParameterizedTest
    @CsvSource({
            "1, Europe",
            "2, Americas",
            "3, Asia",
            "4, Middle East and Africa"})
    public void validateRegionNameTest2(int id, String name) {  ==> iterate 
    each data set one by one 
    		given().pathParam("id", id)
                .when().get("/regions/{id}")
                .prettyPeek()
                .then().assertThat().statusCode(200)
                .and().assertThat().body("region_id", equalTo(id))
                .and().assertThat().body("region_name", equalTo(name));
    }

3.  @ParameterizedTest
    @CsvFileSource(resources = "/regions.csv") ==> uses external csv 
    file which is located under resources directory
    public void validateRegionNameTest3(int id, String name) {
        given().pathParam("id", id)
                .when().get("/regions/{id}")
                .prettyPeek()
                .then().assertThat().statusCode(200)
                .and().assertThat().body("region_id", equalTo(id))
                .and().assertThat().body("region_name", equalTo(name));
    }

data driven testing

Whenever a functionality or a module in an app
requires testing with multiple sets of data (Parametrization),
Multiple inputs then we need to perform data driven testing and
automation.
These scenarios are one of the things That must be automated.
I would do it by seperating Test data from code and stored into external
sources like
Cucumber Examples table, Excel files, CSV files, Database.
Data driven testing has lots of benefits like
More organized, Data centralized, and so on

data driven testing

Whenever a functionality or a module in an app
requires testing with multiple sets of data (Parametrization),
Multiple inputs then we need to perform data driven testing and
automation.
These scenarios are one of the things That must be automated.
I would do it by seperating Test data from code and stored into external
sources like
Cucumber Examples table, Excel files, CSV files, Database.
Data driven testing has lots of benefits like
More organized, Data centralized, and so on

what is data driven testing

Whenever a functionality or a module in an app
requires testing with multiple sets of data (Parametrization),
Multiple inputs then we need to perform data driven testing and
automation.
These scenarios are one of the things That must be automated.
I would do it by seperating Test data from code and stored into external
sources like
Cucumber Examples table, Excel files, CSV files, Database.
Data driven testing has lots of benefits like
More organized, Data centralized, and so on

what is data driven testing

Whenever a functionality or a module in an app
requires testing with multiple sets of data (Parametrization),
Multiple inputs then we need to perform data driven testing and
automation.
These scenarios are one of the things That must be automated.
I would do it by seperating Test data from code and stored into external
sources like
Cucumber Examples table, Excel files, CSV files, Database.
Data driven testing has lots of benefits like
More organized, Data centralized, and so on