JUNIT4 study, in fact, the basic idea is still those, but adopted the new annotation format syntax

See the deep Dive into JUnit 4 (http://www.ibm.com/developerworks/cn/education/java/j-junit4/index.html)

This is mainly about the difference between the new note-based JUnit and the previous 3.x version of JUnit, how to use JUNIT4 to accomplish junit3.x similar work, and what the advantages of using JUNIT4 should be JUnit3. After looking at it, I found out that JUNIT4 is an incompatible version of JUNIT3. Actually JUNIT4 this kind of grammar, feels and NUnit's grammar very much resembles, Java's annotation and C # 's property actually basically is one thing, two languages actually really mutually learns, feels in the language aspect, C # These years progress is faster than Java. Then these days after using Eclipse to create the Activiti project, always prompt the import org.junit can not be resolved. Looking at the dependencies in the Pom file, using the 4.11 version of JUnit, there is no problem, but the project's dependencies are not visible in the workspace of the project. But I created another MAVEN-type project to see the project's dependencies, and I didn't understand why. This is the pain that must be experienced at the beginning after switching a technical route, and it is necessary to keep the principles of these Java infrastructures eclipse/ant/maven/junit/spring and so on, so that the road ahead can be smoother.

JUNIT4 study, in fact, the basic idea is still those, but adopted the new annotation format syntax