Test suites (testng.xml) in Selenium Java - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the <suite> tag in a testng.xml file?

The <suite> tag defines the entire test suite. It groups multiple <test> tags and controls the overall execution of tests in TestNG.

beginner

How do you specify which test classes to run inside a <test> tag in testng.xml?

Inside the <test> tag, use the <classes> tag, and inside it, add one or more <class name="fully.qualified.ClassName"/> tags.

intermediate

What attribute in the <suite> tag controls the parallel execution of tests?

The 'parallel' attribute controls parallel execution. It can be set to 'tests', 'classes', 'methods', or 'instances' to run those elements in parallel.

intermediate

How can you set a timeout for all tests in a test suite using testng.xml?

You can set the 'time-out' attribute inside the <test> tag or use listeners in code. The 'time-out' attribute specifies the max time in milliseconds a test can run.

beginner

Explain the role of the <parameter> tag in testng.xml.

The <parameter> tag allows you to pass values to test methods. You define a name and value in testng.xml, and the test method can receive it using @Parameters annotation.

Which tag in testng.xml defines a group of tests to run together?

A <test>

B <suite>

C <class>

D <methods>

The tag groups multiple tags and defines the whole test suite.

How do you specify a test class to run in testng.xml?

A <class name="fully.qualified.ClassName"/>

B <class>fully.qualified.ClassName</class>

C <testcase>

D <class name="ClassName"/>

Inside , you specify to run that class.

What does setting parallel="methods" in <suite> do?

A Runs all test classes sequentially

B Runs all tests in parallel

C Runs all test methods in parallel

D Runs all test suites in parallel

parallel="methods" runs all test methods in parallel threads.

Where do you define parameters to pass to test methods in testng.xml?

A Inside <suite> or <test> using <parameter>

B Inside <class> tag

C Inside <methods> tag

D Inside <test> using <parameter-set>

Parameters are defined inside or tags using .

What is the default execution order of tests in testng.xml if parallel is not set?

A Parallel execution of tests

B Random execution order

C Depends on JVM

D Sequential execution of tests

By default, tests run sequentially if parallel attribute is not set.

Describe the structure of a basic testng.xml file and explain the role of each main tag.

Think about how you organize tests in groups and classes.

How can you configure parallel execution and parameter passing in testng.xml? Give examples.

Consider how to speed up tests and customize test inputs.

Practice

1. What is the main purpose of the testng.xml file in Selenium testing?

easy

A. To write the Selenium WebDriver code

B. To store test data like usernames and passwords

C. To group and organize test classes and methods to run together

D. To generate HTML reports after test execution

Solution

1. Step 1: Understand the role of testng.xml

   The testng.xml file is used to define which tests to run and how to organize them.

2. Step 2: Identify the main purpose

   It groups test classes and methods so they can be run together as a suite.

3. Final Answer:

   To group and organize test classes and methods to run together -> Option C

4. Quick Check:

   Test suite grouping = To group and organize test classes and methods to run together [OK]

Hint: Remember: testng.xml organizes tests to run as a group [OK]

Common Mistakes:

• Confusing testng.xml with test code files
• Thinking testng.xml stores test data
• Assuming testng.xml generates reports

2. Which of the following is the correct way to define a test suite in testng.xml?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall the correct XML structure for TestNG suites

   The root element is <suite>, inside it we define <test>, then <classes> and <class>.

2. Step 2: Match the options with correct structure

   correctly follows this order and syntax.

3. Final Answer:

   <suite name="MySuite"><test name="Test1"><classes><class name="TestClass"/></classes></test></suite> -> Option A

4. Quick Check:

   Suite > Test > Classes > Class = [OK]

Hint: Remember XML order: suite > test > classes > class [OK]

Common Mistakes:

• Swapping <suite> and <test> tags
• Placing <class> directly under <suite>
• Using wrong tag names or attributes

3. Given the following testng.xml snippet, what tests will run?

<suite name="Suite1" parallel="tests" thread-count="2">
  <test name="TestA">
    <classes>
      <class name="tests.LoginTest"/>
    </classes>
  </test>
  <test name="TestB">
    <classes>
      <class name="tests.PaymentTest"/>
    </classes>
  </test>
</suite>

medium

A. No tests run due to missing methods tag

B. Both LoginTest and PaymentTest run in parallel as separate tests

C. Tests run sequentially, LoginTest then PaymentTest

D. Only LoginTest runs because it is first

Solution

1. Step 1: Analyze the parallel attribute in <suite>

   The attribute parallel="tests" means each <test> runs in parallel threads.

2. Step 2: Identify the tests defined

   There are two tests: TestA with LoginTest class and TestB with PaymentTest class.

3. Final Answer:

   Both LoginTest and PaymentTest run in parallel as separate tests -> Option B

4. Quick Check:

   parallel="tests" runs tests simultaneously = Both LoginTest and PaymentTest run in parallel as separate tests [OK]

Hint: parallel="tests" runs each <test> in parallel [OK]

Common Mistakes:

• Assuming tests run sequentially despite parallel attribute
• Thinking <methods> tag is mandatory to run tests
• Confusing parallel="tests" with parallel="classes"

4. You have this testng.xml file but tests are not running:

<suite name="Suite1">
  <test name="Test1">
    <class name="TestClass">
    </class>
  </test>
</suite>

What is the likely problem?

medium

A. The <suite> tag must include thread-count

B. The <test> tag is missing the parallel attribute

C. The class name must include the package name

D. The <class> tag should be self-closing or empty, not with separate open and close tags

Solution

1. Step 1: Check the <class> tag syntax

   In TestNG XML, <class> should be self-closing like <class name="TestClass"/> or empty without content.

2. Step 2: Identify the error in the given XML

   The given XML uses separate open and close tags for <class> which is invalid and causes tests not to run.

3. Final Answer:

   The <class> tag should be self-closing or empty, not with separate open and close tags -> Option D

4. Quick Check:

   Use self-closing <class> tag = The <class> tag should be self-closing or empty, not with separate open and close tags [OK]

Hint: Use self-closing tag in testng.xml [OK]

Common Mistakes:

• Adding parallel attribute thinking it fixes syntax
• Forgetting package name but that doesn't stop tests
• Assuming thread-count is mandatory

5. You want to run two test classes LoginTest and PaymentTest in parallel but limit total threads to 1 in testng.xml. Which configuration achieves this?

hard

A.

B.

C.

D.

Solution

1. Step 1: Understand parallel and thread-count attributes

   Setting parallel="classes" runs test classes in parallel, and thread-count="1" limits to one thread, so classes run one at a time.

2. Step 2: Check options for matching configuration

   sets parallel to classes and thread-count to 1, matching the requirement.

3. Final Answer:

   Option A configuration runs classes in parallel but limits threads to 1 -> Option A

4. Quick Check:

   parallel="classes" + thread-count=1 = [OK]

Hint: parallel="classes" with thread-count=1 runs classes sequentially [OK]

Common Mistakes:

• Using parallel="tests" with thread-count > 1 runs multiple threads
• Omitting parallel attribute runs tests sequentially
• Confusing parallel="methods" with classes