{"id":3698,"date":"2020-06-11T19:34:46","date_gmt":"2020-06-11T14:04:46","guid":{"rendered":"https:\/\/www.h2kinfosys.com\/blog\/?p=3698"},"modified":"2024-11-04T16:37:47","modified_gmt":"2024-11-04T11:07:47","slug":"testng-test-priority-in-selenium","status":"publish","type":"post","link":"https:\/\/www.h2kinfosys.com\/blog\/testng-test-priority-in-selenium\/","title":{"rendered":"TestNG @Test Priority in Selenium"},"content":{"rendered":"\n

What is Test Priority?<\/strong><\/h2>\n\n\n\n

In TestNG, \u201cPrioritization\u201d means assigning the Execution Priority on Test Case. For example, we want to execute the test cases in order when there are multiple test cases, i.e., first we need to execute the \u201cRegistration\u201d test case before login. The priority on the test case will define the Execution order of Test Case. It can be defined at the Method Level. To assign the priority to a test case, you need to define the test priority at the method level within the @Test annotation. Learning these techniques is an essential part of any Selenium Course<\/a>, where you can gain practical knowledge on test case prioritization and execution flow.<\/p>\n\n\n\n

In order to set the priority, we need to add annotation as @Test (priority=?). The default value for priority will be zero. If you don\u2019t mention the priority, it will take as \u201cpriority=0\u201d for all the test cases and execute. Lower priorities will be executed first. If we define priority as \u201cpriority=\u201d for multiple test cases, then these test cases will get executed only after all the test cases which don\u2019t have any priority and set priority to 0 as the default priority.<\/p>\n\n\n\n

Syntax:<\/strong><\/p>\n\n\n\n

\/\/Valid Syntax<\/strong>\n@Test<\/strong>(priority = 1)\n\/\/Invalid Syntax<\/strong>\n@Test<\/strong>(PRIORITY = 1)<\/pre>\n\n\n\n
TestNG Test Cases without Priority<\/strong><\/h2>\n\n\n\n
Let\u2019s consider below TestNG program <\/a>where we will not define any priority with the test method.<\/p>\n\n\n\n
Step 1:<\/strong> Launch the Eclipse<\/p>\n\n\n\n
package<\/strong> testNGPriority;\n\nimport<\/strong> org.testng.annotations.Test;\n\npublic<\/strong> class<\/strong> NoPriority_Example {\n@Test \npublic<\/strong> void<\/strong> one() \n{ \n  System.out<\/em><\/strong>.println(\"First Test Case\"); \n} \n@Test \npublic<\/strong> void<\/strong> two()\n{ \n  System.out<\/em><\/strong>.println(\"Second Test Case\"); \n} \n@Test \npublic<\/strong> void<\/strong> three()\n{ \n  System.out<\/em><\/strong>.println(\"Third Test Case\"); \n} \n}<\/code><\/pre>\n\n\n\n
Step 2:<\/strong> Right click on Java class > Run As<\/strong> and then click on the TestNG Test<\/strong>.<\/p>\n\n\n\n
Output:<\/strong><\/p>\n\n\n\n
\"NoPriority.PNG\"<\/p>\n\n\n\n
In the above program, we declared a class with three test methods: one()<\/code>, two()<\/code>, and three()<\/code>, each without any assigned priority. When running the tests, we observed that TestNG executed these methods in alphabetical order, following the method names rather than the sequence in which they were implemented in the code. <\/p>\n\n\n\n
This default behavior ensures a predictable, consistent order for execution, even when no specific priority is defined.<\/p>\n\n\n\n
However, to control the execution order according to our specific requirements perhaps starting with essential setup methods or prioritizing critical test cases. we can use the @Test<\/code> annotation to assign priorities explicitly. <\/p>\n\n\n\n
By setting priority values with the @Test<\/code> annotation, we can customize the order to better suit our testing goals, ensuring that key test methods are executed in the desired sequence. This approach provides greater flexibility and control, especially in complex test scenarios where method dependencies or ordered execution are crucial for comprehensive testing.<\/p>\n\n\n\n
How to Set Priority in TestNG for Test Cases?<\/strong><\/h2>\n\n\n\n
Let\u2019s consider below TestNG program where we will define priority with the test methods to execute in sequential order.<\/p>\n\n\n\n
Step 1:<\/strong> Launch the Eclipse<\/p>\n\n\n\n
package<\/strong> testNGPriority;\n\nimport<\/strong> org.testng.annotations.Test;\n\npublic<\/strong> class<\/strong> testNGPriorityExample {\n@Test(priority = 1) \npublic<\/strong> void<\/strong> one() \n{ \n  System.out<\/em><\/strong>.println(\"First Test Case\"); \n} \n@Test(priority = 2) \npublic<\/strong> void<\/strong> two()\n{ \n  System.out<\/em><\/strong>.println(\"Second Test Case\");\n} \n@Test(priority = 3) \npublic<\/strong> void<\/strong> three()\n{ \n  System.out<\/em><\/strong>.println(\"Third Test Case\"); \n} \n}<\/code><\/pre>\n\n\n\n
Step 2:<\/strong> Right click on Java class > Run As<\/strong> and then click on the TestNG Test<\/strong>.<\/p>\n\n\n\n
Output:<\/strong><\/p>\n\n\n\n
\"priorityex.PNG\"<\/p>\n\n\n\n
After assigning the priority to each test method the output has changed. From the above output you can see the test method having lower priority is executed first i.e. execution is happened in sequential order based on priority assigned to the test method.<\/p>\n\n\n\n
Thus, alphabetical order method name has not been considered to the test methods as we provide priorities and all the test cases has got executed.<\/p>\n\n\n\n
Test Methods with Same Priority<\/strong><\/h3>\n\n\n\n
In TestNG, when multiple test methods are assigned the same priority level, TestNG applies a default execution rule to determine their order. <\/p>\n\n\n\n
This allows us to explore how TestNG handles test methods with equal priority values and in what sequence they execute. Let\u2019s look at a TestNG program where we define several test methods with the same priority. <\/p>\n\n\n\n
By observing this program, we can examine TestNG’s execution behavior and understand how it organizes methods alphabetically when priority levels are identical.<\/p>\n\n\n\n
This feature is particularly useful for testers who want a deeper understanding of TestNG\u2019s default ordering mechanism and how it can help achieve consistent, organized test runs even when methods share priority.<\/p>\n\n\n\n
Step 1:<\/strong> Launch the Eclipse<\/p>\n\n\n\n
package<\/strong> testNGPriority;\n\nimport<\/strong> org.testng.annotations.Test;\n\npublic<\/strong> class<\/strong> SamePriorityExample {\n@Test(priority = 1) \npublic<\/strong> void<\/strong> firstTest() \n{ \n  System.out<\/em><\/strong>.println(\"First test method\"); \n} \n@Test(priority = 1) \npublic<\/strong> void<\/strong> secondTest()\n{ \n  System.out<\/em><\/strong>.println(\"Second test method\"); \n} \n@Test(priority = 0) \npublic<\/strong> void<\/strong> thirdTest()\n{ \n  System.out<\/em><\/strong>.println(\"Third test method\"); \n} \n@Test(priority = -1) \npublic<\/strong> void<\/strong> fourthTest()\n{ \n  System.out<\/em><\/strong>.println(\"Fourth test method\"); \n} \n@Test(priority = -2) \npublic<\/strong> void<\/strong> fifthTest()\n{ \n  System.out<\/em><\/strong>.println(\"Fifth test method\"); \n} \n}<\/code><\/pre>\n\n\n\n
Step 2:<\/strong> Right click on Java class > Run As<\/strong> and then click on the TestNG Test<\/strong>.<\/p>\n\n\n\n
Output:<\/strong><\/p>\n\n\n\n
\"samepriority.PNG\"<\/p>\n\n\n\n
In the example provided, we have a class containing five test methods, each assigned specific priority values that determine the execution order in TestNG. TestNG follows a priority-based approach, where lower values have higher execution precedence. However, if two or more methods are assigned the same priority, TestNG defaults to executing those methods in alphabetical order by their method names.<\/p>\n\n\n\n
For instance, in this case, the methods firstTest()<\/code> and secondTest()<\/code> both have a priority value of 1<\/code>. Since these two methods share the same priority, TestNG checks the alphabetical order of their names to decide the execution sequence. <\/p>\n\n\n\n
Here, TestNG detects that firstTest()<\/code> should run before secondTest()<\/code> because the letter ‘f’ comes before ‘s’ alphabetically. This ensures consistency in execution when priority conflicts arise, helping maintain a predictable test order.<\/p>\n\n\n\n
Combination of Prioritized  and Non-prioritized methods<\/strong><\/h3>\n\n\n\n
Let\u2019s consider the following TestNG program where we cover two scenarios within a single TestNG class. First, we have test methods with the same priority value, and second, we include multiple methods without any assigned priority. This setup allows us to observe how TestNG handles tests when there are methods with identical priority levels and methods that lack priority altogether.<\/p>\n\n\n\n
In TestNG, when multiple methods share the same priority, they execute in alphabetical order by their method names. However, if there are also non-prioritized methods in the same class, TestNG will execute these methods last, again in alphabetical order. This behavior illustrates how TestNG\u2019s default execution rules prioritize based on priority values first, then organize remaining non-prioritized tests.<\/p>\n\n\n\n
By experimenting with these configurations, testers can gain a deeper understanding of how TestNG organizes tests and how to use the @Test<\/code> annotation with priority settings effectively, especially when custom execution orders are needed. <\/p>\n\n\n\n
This understanding becomes invaluable for complex test suites, allowing testers to have more control over test execution flow and better manage dependencies between tests.<\/p>\n\n\n\n
Step 1:<\/strong> Launch the Eclipse<\/p>\n\n\n\n
Step 2: <\/strong>Create Class name as \u201cTestNGPriorityTest\u201d<\/p>\n\n\n\n
package<\/strong> testNGPriority;\n\nimport<\/strong> org.testng.annotations.Test;\n\npublic<\/strong> class<\/strong> TestNGPriorityTest {\n@Test \npublic<\/strong> void<\/strong> m1_c() \n{ \n  System.out<\/em><\/strong>.println(\"m1_c\"); \n} \n@Test \npublic<\/strong> void<\/strong> m1_b()\n{ \n  System.out<\/em><\/strong>.println(\"m1_b\"); \n} \n@Test(priority = 1) \npublic<\/strong> void<\/strong> m1_a()\n{ \n  System.out<\/em><\/strong>.println(\"m1_a\"); \n} \n@Test(priority = 1) \npublic<\/strong> void<\/strong> m1_d()\n{ \n  System.out<\/em><\/strong>.println(\"m1_d\"); \n} \n@Test(priority = 0) \npublic<\/strong> void<\/strong> m1_e()\n{ \n  System.out<\/em><\/strong>.println(\"m1_e\"); \n} \n@Test(priority = 2) \npublic<\/strong> void<\/strong> m1_f()\n{ \n  System.out<\/em><\/strong>.println(\"m1_f\"); \n  } \n\n}<\/code><\/pre>\n\n\n\n
Step 2:<\/strong> Right click on Java class > Run As<\/strong> and then click on the TestNG Test<\/strong>.<\/p>\n\n\n\n
Output:<\/strong><\/p>\n\n\n\n
\"priority.PNG\"<\/p>\n\n\n\n
First preference:<\/strong> In the above class, m1_b() and m1_c() which are non-prioritized test methods <\/a>have been executed based on alphabetical order \u2018b\u2019 and then \u2018c\u2019.

Second preference: <\/strong>m1_e() which is prioritized methods has been executed first because of having the highest priority (0). As the test methods m1_a() and m1_d() have the same priority. Therefore, TestNG will considered the alphabetical order of their methods names. So, between them, \u201cm1_a\u201d was executed first and then \u201cm1_d\u201d.<\/p>\n\n\n\n
Third preference:<\/strong>  m1_f() is executed last by TestNG because of having the lowest priority (2).<\/p>\n\n\n\n
Let\u2019s consider the scenario where we automate Google home page and print the title of home page by using the priority feature.<\/strong><\/p>\n\n\n\n
Step 1:<\/strong> Launch the Eclipse<\/p>\n\n\n\n
Step 2:<\/strong> Create the Class name as \u201cGoogleTest\u201d<\/p>\n\n\n\n
package<\/strong> sampletestpackage;\n\nimport<\/strong> org.openqa.selenium.WebDriver;\nimport<\/strong> org.openqa.selenium.chrome.ChromeDriver;\nimport<\/strong> org.testng.annotations.Test;\n\npublic<\/strong> class<\/strong> GoogleTest {\nWebDriver driver;\n@Test(priority = 1) \npublic<\/strong> void<\/strong> driverSetup()\n{ \nSystem.setProperty<\/em>(\"webdriver.chrome.driver\", \"D:\\\\Drivers\\\\geckodriver.exe\");\ndriver=new<\/strong> ChromeDriver(); } \n@Test(priority = 2)\npublic<\/strong> void<\/strong> getURL()\n{ \n  driver.get(\"https:\/\/www.google.com\"); \n} \n@Test(priority = 3) \npublic<\/strong> void<\/strong> getTitle()\n{ \n  String title = driver.getTitle(); \n  System.out<\/em><\/strong>.println(title); \n  } \n@Test(priority = 4) \npublic<\/strong> void<\/strong> closeBrowser()\n{ \n  driver.close(); \n  System.out<\/em><\/strong>.println(\"Test successfully passed\"); \n  } \n}<\/code><\/pre>\n\n\n\n
Output:<\/strong><\/p>\n\n\n\n
\"google.PNG\"<\/p>\n\n\n\n
Conclusion: <\/h2>\n\n\n\n
In TestNG, setting a specific execution order for test methods is straightforward with the use of priorities. By assigning priority values, you can control the sequence in which tests run, ensuring that essential steps are completed in a defined order. <\/p>\n\n\n\n
This approach is particularly valuable for complex test scenarios where certain tests depend on the outcomes of previous ones. With TestNG\u2019s priority feature, creating an organized and efficient testing flow becomes easy, allowing you to manage test dependencies and improve overall test reliability.<\/p>\n\n\n\n
Moreover, when two or more methods share the same priority value, TestNG\u2019s default alphabetical ordering provides an additional layer of control, ensuring a consistent and structured execution sequence. This flexibility in ordering, combined with the use of the Test Annotation in TestNG, not only improves test organization but also minimizes the risk of dependency-related test failures, enhancing the overall stability of your automated test suite.<\/p>\n\n\n\n
For testers and developers working on complex projects, TestNG\u2019s priority feature along with the Test Annotation streamlines the testing process, making it easier to manage and optimize test flows. With careful use of priority settings and Test Annotation, teams can maintain more robust, reliable tests that support seamless development and faster debugging.<\/p>\n\n\n\n
Call to Action<\/strong><\/h2>\n\n\n\n
Ready to take control of your test execution order? At H2K Infosys, our expert-led Selenium courses cover TestNG\u2019s @Test Priority in detail, equipping you with the skills to manage complex test flows, prioritize critical tests, and boost test efficiency. Join H2K Infosys today and unlock the full potential of TestNG <\/strong>@Test Priority in Selenium to advance your career in automation testing!

<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
What is Test Priority? In TestNG, \u201cPrioritization\u201d means assigning the Execution Priority on Test Case. For example, we want to execute the test cases in order when there are multiple test cases, i.e., first we need to execute the \u201cRegistration\u201d test case before login. The priority on the test case will define the Execution order […]<\/p>\n","protected":false},"author":16,"featured_media":3708,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[43],"tags":[976,977,1871,987,313,1870,975,974,1873,1872],"class_list":["post-3698","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-selenium-tutorials","tag-cases-without-priority","tag-prioritized-methods","tag-test-annotation","tag-test-case","tag-test-cases","tag-test-priority","tag-test-priority-in-selenium","tag-testng","tag-testng-for-test-cases","tag-testng-program"],"_links":{"self":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/3698","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/comments?post=3698"}],"version-history":[{"count":0,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/3698\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media\/3708"}],"wp:attachment":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media?parent=3698"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/categories?post=3698"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/tags?post=3698"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}