Shulou(Shulou.com)06/02 Report--

What is the use of TestNG in java? I believe many inexperienced people don't know what to do about it. Therefore, this article summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

1. Introduction of TestNG

TestNG is a testing framework in Java, similar to JUnit and NUnit, with similar functions, but more powerful and easier to use.

For detailed instructions, please refer to the official link: https://testng.org/doc/index.html

II. TestNG installation (based on eclipse+maven)

The following needs to be added to the pom.xml of the project:

Org.testng testng 6.10 test

Remember Maven install.

The installation of the TestNG plug-in in eclipse needs to be done in Help with the address http://beust.com/eclipse; sometimes the URL cannot be opened. This article provides the local download address: https://www.yisu.com/softs/575355.html

III. Basic use and operation of TestNG

Create a new maven project, create a new class of TestNG, you can directly create a new class for use, or you can create a new class of TestNG, as shown below:

The advantage of this method is that when you create a class, you can add all the annotated methods directly, and you can also create a xml. The name path can be defined by yourself. Note that the path to the xml file supports relative paths, and the resulting class file is as follows:

Package com.demo.test.testng;import org.testng.annotations.Test;public class NewTest {@ Test public void f () {}}

A simple use case is as follows:

Package com.demo.test.testng;import org.testng.Assert;import org.testng.annotations.Test;public class NewTest {@ Test public void f () {System.out.println ("this is new test"); Assert.assertTrue (true);}} 1. Run directly:

The results are as follows:

[RemoteTestNG] detected TestNG version 6.10.0

[TestNG] Running:

C:\ Users\ aaa\ AppData\ Local\ Temp\ testng-eclipse-342998054\ testng-customsuite.xml

This is new test

PASSED: f

=

Default test

Tests run: 1, Failures: 0, Skips: 0

=

=

Default suite

Total tests run: 1, Failures: 0, Skips: 0

=

[TestNG] Time taken by org.testng.reporters.JUnitReportReporter@64bfbc86: 4 ms

[TestNG] Time taken by org.testng.reporters.SuiteHTMLReporter@7e0b0338: 26 ms

[TestNG] Time taken by org.testng.reporters.jq.Main@7fac631b: 20 ms

[TestNG] Time taken by [FailedReporter passed=0 failed=0 skipped=0]: 0 ms

[TestNG] Time taken by org.testng.reporters.XMLReporter@23e028a9: 3 ms

[TestNG] Time taken by org.testng.reporters.EmailableReporter2@578486a3: 2 ms

2. Run in xml mode

Because I put xml in another folder, not in the same folder as class, I need to modify the xml as follows:

Operation method:

Right-click the xml and select Run As- > TestNG Suite, as follows:

The running results are as follows:

[RemoteTestNG] detected TestNG version 6.10.0

[TestNGContentHandler] [WARN] It is strongly recommended to add "" at the top of your file, otherwise TestNG may fail or not work as expected.

[XmlSuite] [WARN] 'parallel' value' false' is deprecated, default value will be used instead: 'none'.

[TestNG] Running:

D:\ software\ workspace\ testng\ src\ main\ java\ com\ demo\ test\ testCase\ newTestXML.xml

This is new test

=

Suite

Total tests run: 1, Failures: 0, Skips: 0

=

IV. Notes

TestNG supports a variety of annotations and can be combined as follows

The annotation description @ BeforeSuite runs @ AfterSuite only once before all tests of the suite are run on the annotated method, only once after all tests of the suite run after the annotated method, only once run @ BeforeClass before calling the first test method of the current class, and the annotated method runs @ AfterClass only once after calling the first test method of the current class Annotation methods that run @ BeforeTest annotated methods only once will run @ AfterTest annotated methods before all test methods belonging to classes within the test tag will run @ BeforeGroups configuration methods will run the list of groups before all test methods belonging to classes within the test tag run. This method ensures that the @ AfterGroups configuration method runs the group list shortly before calling the first test method that belongs to any of these groups. This method ensures that running the @ BeforeMethod annotation method shortly after calling the last test method belonging to any of these groups will run the @ AfterMethod annotation method before each test method and will run the @ DataProvider tag after each test method to provide data for the test method. The annotation method must return an Object [] [], where each Object [] can be assigned to the parameter list of the test method. The @ Test method to receive data from the DataProvider needs to mark a method as a factory with the dataProvider name @ Factory equal to the annotation name, and returns the object that TestNG will be used as the test class. The method must return Object [] @ Listeners to define the listener @ Parameters on the test class describes how to pass parameters to the @ Test method @ Test to mark the class or method as part of the test, and if this tag is placed on the class, all public methods of the class will be used as test methods

As in the list above, @ Factory and @ Linsteners are not commonly used.

The first ten annotations don't seem easy to distinguish, and the order is not easy to read, so use the following example to illustrate the code:

Import org.testng.Assert;import org.testng.annotations.AfterClass;import org.testng.annotations.AfterGroups;import org.testng.annotations.AfterMethod;import org.testng.annotations.AfterSuite;import org.testng.annotations.AfterTest;import org.testng.annotations.BeforeClass;import org.testng.annotations.BeforeGroups;import org.testng.annotations.BeforeMethod;import org.testng.annotations.BeforeSuite;import org.testng.annotations.BeforeTest;import org.testng.annotations.Test Public class NewTest {@ Test (groups= "group1") public void test1 () {System.out.println ("test1 from group1"); Assert.assertTrue (true);} @ Test (groups= "group1") public void test11 () {System.out.println ("test11 from group1"); Assert.assertTrue (true) } @ Test (groups= "group2") public void test2 () {System.out.println ("test2 from group2"); Assert.assertTrue (true);} @ BeforeTest public void beforeTest () {System.out.println ("beforeTest");} @ AfterTest public void afterTest () {System.out.println ("afterTest") @ BeforeClass public void beforeClass () {System.out.println ("beforeClass");} @ AfterClass public void afterClass () {System.out.println ("afterClass");} @ BeforeSuite public void beforeSuite () {System.out.println ("beforeSuite");} @ AfterSuite public void afterSuite () {System.out.println ("afterSuite") } / / valid only for group1, i.e. test1 and test11 @ BeforeGroups (groups= "group1") public void beforeGroups () {System.out.println ("beforeGroups");} / / only valid for group1, that is, test1 and test11 @ AfterGroups (groups= "group1") public void afterGroups () {System.out.println ("afterGroups");} @ BeforeMethod public void beforeMethod () {System.out.println ("beforeMethod") } @ AfterMethod public void afterMethod () {System.out.println ("afterMethod");}}

The running results are as follows:

BeforeSuite

BeforeTest

BeforeClass

BeforeGroups

BeforeMethod

Test1 from group1

AfterMethod

BeforeMethod

Test11 from group1

AfterMethod

AfterGroups

BeforeMethod

Test2 from group2

AfterMethod

AfterClass

AfterTest

PASSED: test1

PASSED: test11

PASSED: test2

=

Default test

Tests run: 3, Failures: 0, Skips: 0

=

AfterSuite

Compared with the previous instructions, we should be able to get a better understanding.

5. TestNG assertion

There are many kinds of TestNG assertions, including equal / unequal, true/false, null/ is not null, same / different, and so on.

VI. Expected exception test of TestNG

The expected exception test is added by adding the expected Exception after the @ Test annotation. The example is as follows:

@ Test (expectedExceptions = ArithmeticException.class) public void divisionWithException () {int I = 1 / 0; System.out.println ("After division the value of i is:" + I);}

The running results are as follows:

[RemoteTestNG] detected TestNG version 6.10.0

[TestNG] Running:

C:\ Users\ Administrator\ AppData\ Local\ Temp\ testng-eclipse--754789457\ testng-customsuite.xml

PASSED: divisionWithException

=

Default test

Tests run: 1, Failures: 0, Skips: 0

=

=

Default suite

Total tests run: 1, Failures: 0, Skips: 0

=

[TestNG] Time taken by org.testng.reporters.JUnitReportReporter@55d56113: 0 ms

[TestNG] Time taken by org.testng.reporters.SuiteHTMLReporter@1e127982: 0 ms

[TestNG] Time taken by org.testng.reporters.jq.Main@6e0e048a: 32 ms

[TestNG] Time taken by [FailedReporter passed=0 failed=0 skipped=0]: 0 ms

[TestNG] Time taken by org.testng.reporters.XMLReporter@43814d18: 0 ms

[TestNG] Time taken by org.testng.reporters.EmailableReporter2@6ebc05a6: 0 ms

7. TestNG ignores testing

Sometimes we write a use case that is not ready, or the test does not want to run this use case, so it is obviously unwise to delete it, so we can ignore it by annotating @ Test (enabled = false), and this use case will not run, as shown in the following example:

Import org.testng.annotations.Test;public class TestCase1 {@ Test (enabled=false) public void TestNgLearn1 () {System.out.println ("this is TestNG test case1");} @ Test public void TestNgLearn2 () {System.out.println ("this is TestNG test case2");}}

Running result:

This is TestNG test case2

PASSED: TestNgLearn2

8. TestNG timeout test

Timeout means that if the unit test takes more than the specified number of milliseconds, TestNG will abort it and mark it as a failure. This item is often used for performance testing. The following is an example:

Import org.testng.annotations.Test;public class TestCase1 {@ Test (timeOut = 5000) / / time in mulliseconds public void testThisShouldPass () throws InterruptedException {Thread.sleep (4000);} @ Test (timeOut = 1000) public void testThisShouldFail () {while (true) {/ / do nothing}

The results are as follows:

PASSED: testThisShouldPass

FAILED: testThisShouldFail

Org.testng.internal.thread.ThreadTimeoutException: Method com.demo.test.testng.TestCase1.testThisShouldFail () didn't finish within the time-out 1000

At com.demo.test.testng.TestCase1.testThisShouldFail (TestCase1.java:37)

At sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethod)

At sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

At sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

At java.lang.reflect.Method.invoke (Method.java:498)

At org.testng.internal.MethodInvocationHelper.invokeMethod (MethodInvocationHelper.java:104)

At org.testng.internal.InvokeMethodRunnable.runOne (InvokeMethodRunnable.java:54)

At org.testng.internal.InvokeMethodRunnable.run (InvokeMethodRunnable.java:44)

At java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)

At java.util.concurrent.FutureTask.run (FutureTask.java:266)

At java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)

At java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)

At java.lang.Thread.run (Thread.java:748)

IX. Group testing

The grouping test is to use group, and if you use xml, it is the tag inside. If it is directly in class, it is grouped through @ Test (groups= "group2"). For example, the example in the note in section 4 is divided into two group, and @ BeforeGroup needs to add a group name before it can be properly mounted under the group.

This group specification can be on a single test method or on class. As long as the same group name is in the same group, and there can be multiple group names, such as @ Test (groups = {"mysql", "database"}), the example is as follows:

A test file NewTest.class:

Public class NewTest {@ Test (groups= "group1") public void test1 () {System.out.println ("test1 from group1"); Assert.assertTrue (true);} @ Test (groups= "group1") public void test11 () {System.out.println ("test11 from group1"); Assert.assertTrue (true) } @ Test (groups= "group2") public void test2 () {System.out.println ("test2 from group2"); Assert.assertTrue (true);} @ BeforeTest public void beforeTest () {System.out.println ("beforeTest");} @ AfterTest public void afterTest () {System.out.println ("afterTest") @ BeforeClass public void beforeClass () {System.out.println ("beforeClass");} @ AfterClass public void afterClass () {System.out.println ("afterClass");} @ BeforeSuite public void beforeSuite () {System.out.println ("beforeSuite");} @ AfterSuite public void afterSuite () {System.out.println ("afterSuite") @ BeforeGroups (groups= "group1") public void beforeGroups () {System.out.println ("beforeGroups");} @ AfterGroups (groups= "group1") public void afterGroups () {System.out.println ("afterGroups");} @ BeforeMethod public void beforeMethod () {System.out.println ("beforeMethod") } @ AfterMethod public void afterMethod () {System.out.println ("afterMethod");}}

Another TestCase1.class:

Test (groups= "group2") public class TestCase1 {@ Test (enabled=false) public void TestNgLearn1 () {System.out.println ("this is TestNG test case1");} @ Test public void TestNgLearn2 () {System.out.println ("this is TestNG test case2");}}

Xml is as follows:

The running results are as follows:

BeforeSuite

BeforeTest

BeforeClass

BeforeGroups

BeforeMethod

Test1 from group1

AfterMethod

BeforeMethod

Test11 from group1

AfterMethod

AfterGroups

BeforeMethod

Test2 from group2

AfterMethod

AfterClass

This is TestNG test case2

AfterTest

AfterSuite

As shown above, you run two use cases of group1 and then two use cases of group2

Note that when you identify group in xml, you need to add the group to be run, and also add the class that identifies these group. Those that are not added will not run.

10. Suite test

A test suite is a collection of test cases used to test the behavior or a set of behaviors of a software program. In TestNG, we cannot define a suite in the test source code, but it can be represented by a XML file because the suite is an executive function. It also allows flexibility to configure the tests to run. A suite can contain one or more tests and are defined by tags. Is the root tag of testng.xml. It describes a test suite, which consists of several parts.

The following table lists the legal attributes of all accepted definitions.

Property describes the name of the name suite, which is a level or level of detail that forces the property verbose to run, with a level of 0-10, of which 10 is the most detailed whether parallelTestNG is running a different thread to run the suite. The default is none, and the other levels are methods, tests, classes, instancesthread-count if parallel mode is enabled (ignore other ways) The default timeout for all test methods used by annotations is the default timeout type time-out used in all test methods in this test.

Sometimes we may need to call the methods in the test case in a specific order, or we may want to share some data and state between the methods. TestNG supports this dependency because it supports the declaration of explicit dependencies between test methods.

TestNG allows you to specify dependencies:

Use the attribute dependsOnMethods in the @ Test annotation

Use the attribute dependsOnGroups in the @ Test annotation

In addition, dependencies are divided into hard dependency and soft dependency:

Hard dependency: default to this dependency mode, that is, all its dependent methods or groups must be pass, otherwise the identified dependent class or method will be skipped and identified as skip in the report. As shown in the following example, this is the default dependency mode.

Soft dependency: in this way, not all pass of the dependent method or group will not affect the operation of the identified dependent class or method. Note that if you use this method, there must be no causal relationship between success and failure between the dependent and the dependent, otherwise it will cause the use case to fail. This method needs to add alwaysRun=true to the annotations, such as @ Test (dependsOnMethods= {"TestNgLearn1"}, alwaysRun=true).

In TestNG, we use dependOnMethods and dependsOnGroups to implement dependency testing. And both of them support regular expressions, as shown in example 3. Here are several usage examples:

Example 1, dependent method pass:

Public class TestCase1 {@ Test (enabled=true) public void TestNgLearn1 () {System.out.println ("this is TestNG test case1");} @ Test (dependsOnMethods= {"TestNgLearn1") public void TestNgLearn2 () {System.out.println ("this is TestNG test case2");}}

Running result:

This is TestNG test case1

This is TestNG test case2

PASSED: TestNgLearn1

PASSED: TestNgLearn2

Example 2, dependent method fail:

Public class TestCase1 {@ Test (enabled=true) public void TestNgLearn1 () {System.out.println ("this is TestNG test case1"); Assert.assertFalse (true);} @ Test (dependsOnMethods= {"TestNgLearn1"}) public void TestNgLearn2 () {System.out.println ("this is TestNG test case2");}}

Results:

This is TestNG test case1

FAILED: TestNgLearn1

Junit.framework.AssertionFailedError

At junit.framework.Assert.fail (Assert.java:47)

At junit.framework.Assert.assertTrue (Assert.java:20)

At junit.framework.Assert.assertFalse (Assert.java:34)

At junit.framework.Assert.assertFalse (Assert.java:41)

At com.demo.test.testng.TestCase1.TestNgLearn1 (TestCase1.java:26)

At sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethod)

At sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

At sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

At java.lang.reflect.Method.invoke (Method.java:498)

At org.testng.internal.MethodInvocationHelper.invokeMethod (MethodInvocationHelper.java:104)

At org.testng.internal.Invoker.invokeMethod (Invoker.java:645)

At org.testng.internal.Invoker.invokeTestMethod (Invoker.java:851)

At org.testng.internal.Invoker.invokeTestMethods (Invoker.java:1177)

At org.testng.internal.TestMethodWorker.invokeTestMethods (TestMethodWorker.java:129)

At org.testng.internal.TestMethodWorker.run (TestMethodWorker.java:112)

At org.testng.TestRunner.privateRun (TestRunner.java:756)

At org.testng.TestRunner.run (TestRunner.java:610)

At org.testng.SuiteRunner.runTest (SuiteRunner.java:387)

At org.testng.SuiteRunner.runSequentially (SuiteRunner.java:382)

At org.testng.SuiteRunner.privateRun (SuiteRunner.java:340)

At org.testng.SuiteRunner.run (SuiteRunner.java:289)

At org.testng.SuiteRunnerWorker.runSuite (SuiteRunnerWorker.java:52)

At org.testng.SuiteRunnerWorker.run (SuiteRunnerWorker.java:86)

At org.testng.TestNG.runSuitesSequentially (TestNG.java:1293)

At org.testng.TestNG.runSuitesLocally (TestNG.java:1218)

At org.testng.TestNG.runSuites (TestNG.java:1133)

At org.testng.TestNG.run (TestNG.java:1104)

At org.testng.remote.AbstractRemoteTestNG.run (AbstractRemoteTestNG.java:114)

At org.testng.remote.RemoteTestNG.initAndRun (RemoteTestNG.java:251)

At org.testng.remote.RemoteTestNG.main (RemoteTestNG.java:77)

SKIPPED: TestNgLearn2

Example 3. Group dependency:

As shown below, method1 relies on all methods whose group name is init:

Test (groups = {"init"}) public void serverStartedOk () {} @ Test (groups = {"init"}) public void initEnvironment () {} @ Test (dependsOnGroups = {"init.*"}) public void method1 () {}

Here, the execution order of the two methods in the init group cannot be guaranteed if it is not specified in the xml.

XII. Parametric testing

Another interesting feature in TestNG is parametric testing. In most cases, you will encounter scenarios where business logic requires a lot of testing. Parameterized tests allow developers to run the same tests again and again with different values.

TestNG can pass parameters directly to the test method in two different ways:

Use testng.xml

Using a data provider

Two methods of passing parameters are described below:

1. Use textng.xml to transfer parameters

The example code is as follows:

Public class TestCase1 {@ Test (enabled=true) @ Parameters ({"param1", "param2"}) public void TestNgLearn1 (String param1, int param2) {System.out.println ("this is TestNG test case1, and param1 is:" + param1+ "; param2 is:" + param2); Assert.assertFalse (false);} @ Test (dependsOnMethods= {"TestNgLearn1"}) public void TestNgLearn2 () {System.out.println ("this is TestNG test case2") }}

Xml configuration:

Run xml and the result is as follows:

This is TestNG test case1, and param1 is:1011111; param2 is:10

This is TestNG test case2

=

Suite

Total tests run: 2, Failures: 0, Skips: 0

=

2. Use @ DataProvider to pass parameters

It should be noted here that the type of parameter passed must be consistent, and that a function with @ DataProvider annotation must return Object [] [].

The code is as follows:

Public class TestCase1 {@ DataProvider (name = "provideNumbers") public Object [] [] provideData () {return new Object [] [] {{10,110}, {200,210};} @ Test (dataProvider = "provideNumbers") public void TestNgLearn1 (int param1, int param2) {System.out.println ("this is TestNG test case1, and param1 is:" + param1+ "; param2 is:" + param2 ") Assert.assertFalse (false); @ Test (dependsOnMethods= {"TestNgLearn1"}) public void TestNgLearn2 () {System.out.println ("this is TestNG test case2");}}

When you run this class, the result is:

This is TestNG test case1, and param1 is:10; param2 is:20

This is TestNG test case1, and param1 is:100; param2 is:110

This is TestNG test case1, and param1 is:200; param2 is:210

This is TestNG test case2

PASSED: TestNgLearn1 (10,20)

PASSED: TestNgLearn1 (100110)

PASSED: TestNgLearn1 (200,210)

PASSED: TestNgLearn2

XIII. Description of XML configuration file

Most of the above are run on the basis of test scripts, and a few of them are run on xml. Here we will explain it with xml:

Each label is explained as follows:

1. Suite tag

The outermost tag of the testNG.xml file is suite, that is, the test suite, under which there can be multiple sums, and several attributes that can be added are described in the sub-suite test in section 10. Here is a detailed description:

(1), name attribute

This property is required, and the value can be set by yourself. This name will be seen in the testNG report.

(2), verbose attribute

This property specifies the detail level of the testNG report, starting from 0 to 10, where 10 is the most detailed, and the default generated xml this property value is 1

(3), parallel attribute

This attribute refers to the proxy operation mode, which defaults to none, that is, serial operation mode. Parallel execution methods include the following, which are described below:

Methods: method level. At this value, all test methods under this suite will be multithreaded, that is, multithreading at the test case level. If there are dependencies between use cases, the execution order will run according to the set dependencies

Tests:TestNG will run all the methods in the same tag in the same thread, and each tag will be in a separate thread, which allows you to group all classes that are not thread-safe in the same thread and ensure that they will all run in the same thread, while using TestNG to run tests with as many threads as possible.

Classes: class-level concurrency, that is, TestNG will run each class under the suite in a separate thread, and all use cases under the same class will run in the same thread

Instances: instance level, that is, TestNG will run all methods in the same instance in the same thread, and two methods on two different instances will run in different threads.

(4), thread-count attribute

This property is used to specify the number of threads. Enter it as needed and add it only if the parallel parameter is not none.

(5), annotations attribute

This item is the annotated level, methods level and class level, and generally does not need to be set.

(6), time-out attribute

This property is used to specify the timeout, the timeout for all use cases under the suite

(7), group-by-instances attribute

This item is used for dependent methods, and the dependent object has multiple overloaded objects, because if it is a dependent method, and the method has multiple overloaded methods, the default is to run all the overloaded methods before running the dependent methods, but sometimes we don't want to, just set this to true.

(8), preserve-order attribute

Value can be true or false. If true, the use case execution will be executed in the order in xml, otherwise it will be executed out of order. If this attribute is not added, it will be executed sequentially by default.

2. Test tag

This tag has no special meaning and can include multiple tags, such as groups, classes, etc. The following writing methods are described below:

Select all test scripts in a package (including subpackages)

Select part of the test script in a class

Exclude some groups in a package

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.