Skip to main content

Quality Assurance

Exploring Test Level and Suite Level Parameterization in TestNG

Multiracial Portuguese Jamaican mid adult businessman with beard standing smiling at desk with laptop reviewing data in bright business office wearing suit

Parameterization in test automation is a crucial technique that enables testers to execute the same test with different data sets or configurations, enhancing flexibility and test coverage. By using parameterized tests, testers can run a single test multiple times with various inputs, thereby improving the comprehensiveness of testing. This approach saves time and effort by allowing for the testing of numerous scenarios and inputs without the need to create separate tests for each case. In TestNG, parameterization can be implemented at both the test and suite levels, offering flexibility in passing values to test methods.

Test Level Parameterization

Test-level parameterization involves passing different values to the same test method. This approach is particularly useful when you want to execute the same test logic with multiple sets of input data. TestNG provides the ‘@DataProvider’ annotation to achieve this.

Example 1: Testing Login with Multiple User Credentials

Suppose we want to test a login functionality with different user credentials. We can create a data provider method and annotate our test method to use this data provider:

import org.testng.annotations.DataProvider;
import org.testng.annotations.Test;

public class TestLevelParameterizationExample {

    @DataProvider(name = "loginData")

    public Object[][] loginData() {

        return new Object[][] {

            {"user1", "password1"},

            {"user2", "password2"},

            {"user3", "password3"}



    @Test(dataProvider = "loginData")

    public void testLogin(String username, String password) {

        // Implement login test logic using username and password

        System.out.println("Testing login with username: " + username + " and password: " + password);


In this example, the ‘@DataProvider’ method ‘loginData’ provides multiple sets of credentials, and the ‘@Test’ method ‘testLogin’ is executed for each set.

Suite Level Parameterization

Suite-level parameterization allows you to pass parameters to the entire test suite. This is helpful when you want to configure test suite properties or settings that apply to all the tests within the suite. You can specify suite-level parameters in your testng.xml configuration file.

Example 2: Configuring Browser and Environment for Test Suite

Let’s say you want to run your test suite on different browsers and environments (e.g., QA and production). You can define these parameters in your testng.xml file:

<suite name="MyTestSuite">

    <parameter name="browser" value="chrome"/>

    <parameter name="environment" value="qa"/>

    <test name="Test1">


            <class name="SuiteLevelParameterizationExample"/>




This example defines the ‘browser’ and ‘environment’ parameters at the suite level. To access these parameters in your test classes, you can use the ‘@Parameters’ annotation:

import org.testng.annotations.Parameters;
import org.testng.annotations.Test;

public class SuiteLevelParameterizationExample {

    @Parameters({"browser", "environment"})


    public void configureTest(String browser, String environment) {

        // Configure test settings based on the provided parameters

        System.out.println("Configuring test with browser: " + browser + " and environment: " + environment);




In this example, the ‘configureTest’ method retrieves the ‘browser` and ‘environment’ parameters and uses them to configure the test.

Let’s clarify the key differences between test-level parameterization and suite-level parameterization in TestNG:

Test Level Parameterization vs. Suite Level Parameterization

Test Level Parameterization Attributes:

  1. Scope: Test-level parameterization allows you to pass different values to individual test methods within a test class. Each test method can have its unique set of data.
  2. Annotation: It is achieved using the @DataProvider annotation, which defines a method that supplies data to the test method annotated with @Test(dataProvider = “dataProviderMethodName”).
  3. Example: In the example provided, the @DataProvider method loginData supplies data to the testLogin method. Each set of credentials is used for a separate execution of testLogin.
  4. Flexibility: Test-level parameterization is more flexible when different data are needed for different test methods within the same test class.

Suite Level Parameterization Attributes:

  1. Scope: Suite-level parameterization allows you to pass parameters that apply to the entire test suite. These parameters are shared among all the tests within the suite.
  2. Configuration: It is configured in the testng.xml file using the <parameter> elements, where you define parameter names and values for the entire suite.
  3. Access: You can access suite-level parameters using the @Parameters annotation in your test classes. All test methods within the suite can access the same set of parameters.
  4. Example: In the example provided, the suite-level parameters browser and environment are defined in the testng.xml file and accessed by the configureTest method in the SuiteLevelParameterizationExample class. These parameters apply to all tests within the suite.
  5. Use Cases: Suite-level parameterization is useful for configuring global settings, such as specifying a common browser or environment for all tests in the suite. It’s suitable when you want to maintain consistency across multiple tests.


Parameterization is a crucial aspect of test automation that enhances the versatility and coverage of your tests. In TestNG, you can implement parameterization at both the test and suite levels. Test-level parameterization allows you to pass different data to the same test method, while suite-level parameterization enables you to configure test suite properties. By mastering these techniques, you can write more robust and flexible automated tests to validate your application’s functionality under various conditions.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Sanket Dudhe

Sanket Dudhe is an Associate Technical Consultant at Perficient. He has an experience of 4+ years as SDET. He loves technology and hence is curious to learn about new emerging technologies #lovefortechnology.

More from this Author

Follow Us