Скачать или смотреть How to Re-run a Complete Test Suite Using TestNG Without a Listener

Discover a straightforward method to handle TestNG test failures by re-running an entire test suite from within the test methods without using listeners.
---
This video is based on the question https://stackoverflow.com/q/68066910/ asked by the user 'Aman Khan' ( https://stackoverflow.com/u/11061356/ ) and on the answer https://stackoverflow.com/a/68096574/ provided by the user 'Gautham M' ( https://stackoverflow.com/u/7804477/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to re run suite without using listener in testng

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Re-run a Complete Test Suite Using TestNG Without a Listener

When running automated tests using TestNG, one common challenge can be handling test failures. Imagine you have a complete test suite, and one or more of your test cases fail. How do you rerun the entire suite efficiently without using listeners? In this guide, we'll guide you through a solution that meets this requirement, allowing for an organized and effective re-test without complicating your workflow.

The Challenge: Rerunning a Complete Suite

You might find yourself in a situation where:

You want to rerun an entire suite when any test case fails.

You need to check for failures at the end of a specific test method since you cannot use @ AfterClass or @ AfterMethod due to other functionalities in play.

You might be considering whether to use a listener to track failed tests, but you prefer to keep it simple without additional dependencies.

The Solution: Utilizing @ AfterSuite Method

To solve this problem, we can leverage the @ AfterSuite method in TestNG. This approach allows us to check the results of the entire execution and rerun the suite if necessary. Here’s how to implement it step-by-step:

Step 1: Setting Up Your Test Class

In your test class, declare two static integer variables: one to count the number of re-runs and another to specify the maximum allowed re-runs.

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Implementing the @ AfterSuite Method

Next, implement the @ AfterSuite method where you will check if there are any failed tests. If there are fails and the maximum rerun count has not been reached, the suite will rerun.

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Running Your Tests

With this setup, after your suite execution completes, the @ AfterSuite method will check the test results. If there are failures, it will automatically rerun the entire suite up to the specified maximum rerun count.

Conclusion

Rerunning a test suite in TestNG without the use of listeners is entirely feasible with the right approach. By implementing an @ AfterSuite method, you can efficiently manage test failures and ensure that your test suite executes safely and effectively without any additional overhead.

Now you're equipped with the knowledge to handle test failures more dynamically. Implement this strategy and improve your test automation efforts. Happy testing!