Create TestNG Project In Eclipse & Run Selenium Test Script

Step 3: Creating a TestNG class in Eclipse

Creating a TestNG class is as easy as creating a Java class. All you need to do is follow the steps mentioned below and have your first testNG class ready.

• Navigate to src from the project folder and right-click the same. You will see TestNG as an option in the dropdown towards the bottom. Click on it and you will now see two sub-options to either create a TestNG class or convert the class to TestNG. As we are creating a new TestNG class, you need to select the first option.

  

• Generally, the source folder name is auto-filled but if it is not, you can simply browse through the same. Next, you can give any name to your class, for example, ‘TestNGTestOne’ and its package. For now, we will keep the basic annotations selected @BeforeMethod and @AfterMethod. However, Annotations can be configured at a later stage as well depending upon your test scenario. If you wish to configure them now, you can refer to the TestNG annotations.

  

• You will now see a class(TestNGTestOne.java) in your project directory with default methods, viz f(), as well as beforeMethod() and afterMethod() that you can see were checked in the screenshot above.

  

You are now all set to write code in your first TestNG class, but before doing so let me quickly brief you about the TestNG annotations that we can see in the class we just created.

• @Test annotation implies that the method is a test method and any code written under it constitutes to be a test case.
• @BeforeMethod implies that the method beneath should be running before the test method.
• @AfterMethod, just as the name suggests implies that the method should run after the test method.

Watch this video to learn about the TestNG Annotations and how they help provide better structure and readability to the code.

TestNG Reports and Results

After Run As TestNG Test, the Console shows the pass, fail, and skip counts, and Eclipse writes index.html and emailable-report.html into the project's test-output folder. The TestNG reports chapter explains those files and how to publish them from Jenkins.

Can AI Coding Assistants Debug A Failing TestNG Script?

AI coding assistants like GitHub Copilot, Cursor, and Claude Code can read a failing TestNG stack trace and suggest a fix in the same editor where you wrote the test class.

These tools match the exception in the console or the XML report under test-output back to the exact line in your Test Class, then propose a change such as replacing a fixed Thread.sleep with an explicit WebDriverWait. They can also flag a missing @Test annotation on a method before you even run the suite, since Eclipse still compiles a plain method with no annotation. Some setups go further and let an agent open the TestNG-generated HTML report through a Model Context Protocol server and read it directly, instead of you pasting the trace into a chat window.

The limitation is that a single failed run does not tell the assistant whether the locator was wrong or the page was just slow to load that one time. It cannot see the browser session that already closed, so a suggested wait value or selector change is a guess until you rerun the TestNG suite and confirm the same test passes on a second run. Treat every AI-suggested fix to a Selenium TestNG test as unverified until the suite reruns clean.

Bonus Pointer: Use A Cloud Selenium Grid For Parallel Testing

Kudos on creating the TestNG project in Eclipse and running the Selenium TestNG script. Right now you have triggered the Selenium TestNG script using a Selenium WebDriver in your own machine but that isn’t a scalable approach. It’s okay if you’re a novice at Selenium testing. However, after some time your test suites are bound to get bigger as you may have to run automated browser testing over dozens or maybe hundreds of browsers + OS combinations.

Doing so with Selenium WebDriver can consume a lot of time and effort because the tests will be queued and executed one after another.

This is where you can leverage a Selenium Grid which can allow you to run these test cases in parallel. So read this Selenium Grid tutorial and fasttrack your Selenium testing experience like a pro!

If you’re already familiar with Selenium Grid and have it set up in your system, even then there are going to be scale issues. You will need to expand the Selenium Grid with new devices and browsers that would be launched in the market. And that would require a lot of investment in hardware and maintenance of your local Selenium Grid. Which is why it is recommended to use a cloud Selenium Grid like TestMu AI.

TestMu AI will help you trigger your Selenium tests with TestNG over 3000+ real browsers and operating systems. That way, you won’t even have to worry about which browsers are new in the market or maintaining your in-house Selenium infrastructure so you could focus on writing better Selenium testing scripts.

In order to run your same script on TestMu AI Selenium Grid, you will need to sign up with TestMu AI(Its FREE) and do a couple of changes to your project setup. Run your TestNG scripts on Selenium Grid Cloud. Happy Testing!