static-defined classes, you can easily debug with your favorite debugging program. (The example used in this article assumes that Eclipse IDE is used. However, the technology I described here can be used in most other ides without many modifications .) When making any design decision, you must weigh the impact of the selection and decision. Here, in order to obtain the ability to debug dynamically generated test
field of automated testing, for the same unit of testing, often there are multiple test cases, at the code level, the implementation of multiple test cases, characterized by: the same logic, the data is different. In this case, it is necessary to use the parameterized operation, to some extent to achieve the separation of co
framework
First, we provide an example of using the new extension for parallel testing.
Example 1. Use JUnit extension for parallel testing
/** * @author Zhi Gan * */ @RunWith(Parallelized.class) @ParallelSetting(threadNumber = { 1, 2, 4, 8 }) public class TestThreaded { Set @Before public void setUp() { strSet = new LockFreeSet(); } @
int Add (int a, int b)
{
return a + b;
}
public int subtract (int a, int b)
{return a-a
;
}
public int multiply (int a, int b)
{
return a * b;
}
public int divide (int a, int b)
{
return a/b;
}
}
2. Add the JUnit library
Then in order to use JUnit, you need to join the library:
Right-click on the project properties-
classes, this test class cannot be injected with a simulated Intent.5. ActivityInstrumentationTestCase2 -- test the class of a single Activity in a normal system environment. You cannot inject a simulated Context, but you can inject a simulated Intent. In addition, you can run the test method in the UI thread (the main thread of the Application), and send button
, Calculate.sub (4, 3));//test}}We are interested in in-depth research and can understand:JUnit itself is designed around two design patterns: the command mode (junit test case) and the Integrated mode (JUnit test Suite).Simply put: The
1. Learn the use of the JUnit frameworkYou can learn from the following two examples.A, JUnit use Method Example 11) bring JUnit into the current project libraryCreate a new Java Project-cooljunit, open the Project Cooljunit's property page, select the Java Build Path Sub-option, click the "Add Library ..." button, an
following is the sample code for creating a test suite class in junit4.x.
Package COM. jadyer. junit4;
The following is the sample code for creating a test suite class in junit3.8.Package COM. jadyer. junit3;
Parameterization test of junit4.xTo ensure the rigor of unit
test classes and write countless test methods to ensure the effectiveness of the programs we've developed.2 Introduction to JUnit basic annotationsExecuted once before all test methods, typically in which the overall initialization code is written@BeforeClassExecutes once a
Because in the program, an interface corresponds to an implementation method, and in the interface often defines a number of related methods, so at the time of testing, if all in the main method inside the test, the main method will appear bloated, and it is not easy for other people to test and view the test data, with JUnit
Today is the software test on the computer, the main content is the installation of JUnit and a simple class of test practice. The teacher recommended eclipse, but I used toUsing INTELLJ idea, so I tried INTELLJ idea for JUnit's installation. The procedure is described below.Installation:Intellj idea comes with the JUnit
time you want to set, in milliseconds, so 1000 represents 1 seconds.Third, Test Exception Exception handling in JAVA is also a priority, so you will often write some functions that need to throw exceptions. So, if you think a function should throw an exception, but it's not thrown, does that count as a Bug? This is certainly a bug, and JUnit has taken this into account to help us find this bug. For
In the "programmers who don't write unit tests are not good programmers" principle, I'm sticking with the unit test, not saying that all Java Web applications are based on spring, but at least more than half are spring-based. After discovering bean management through spring, there are a variety of deficiencies in testingFor example, when many people do unit tests, they also initialize the spring container i
, negative, and zero. So let's proceed as follows. First, right-click a new juint test case in the calculator class and name it calculatorsquaretest. Then the code of this class is modified as follows:
1 package Org. logback. test; 2 3 Import static Org. JUnit. assert. *; 4 5 import Java. util. arrays; 6 Import Java. u
. Although this can also determine whether to perform the expected exception, but it still has drawbacks, the next will be a comparison to know that, Try...catch method, JUnit can not give you a detailed assertion failure reasons.So what can you do to test the anomaly since JUnit 4? Use @Test (execpted=exception.class)
gives us extra work for our development. Here we have an idea to do a global unit test program to automatically retrieve all of the JUnit test test programs in the project set. This global unit test program will be run based on JUNIT4.
Core mechanism: JUNIT4 supports runni
Direct use of JUnit to test the shortage of Spring programs
you need to manually fetch the bean using hard coding: in the test case, we need to get the target Bean to be tested from the SPIRNG container by means of the Applicationcontext.getbean () method, and also to do the modeling operation.
The database site is vulnerable to damage: The
classes, directories, and packages to add or exclude tests in a package. However, if you choose to use Jython, you can use the entire Python language and runtime to resolve the problem of which tests you choose to perform. Python scripts are much more flexible than Java property files, and are limited by your imagination.
The seamless integration of Jython with the Java platform enables the creation of statically defined, dynamically constructed TestSuite classes. There are a lot of tutorials
class writing SRC package, the code attached to the last side of the code area;2) Then write the test class, generally re-build a TESTSRC package (with the SRC package sibling), and then build the test class under the TESTSRC;3) Run the test method in the
5.10-rerunning failed Tests
When a test in a suite fails, each testng creates a file named Testng-failed.xml in the output directory. This XML file contains the necessary information to rerun only these failed test methods, allowing only those failed tests to run without having to run all the tests. Thus, a typical scenario would be this:
java -classpath testng.jar;%CLASSPATH% org.testng.TestNG -d
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.