root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

SPR-6092: clarify jar name in test docs

This commit is contained in:
David Syer 2009-12-04 15:21:51 +00:00
parent 5013664ec5
commit fae06dc156
1 changed files with 16 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
spring-framework-reference/src/testing.xml
View File

@ -155,16 +155,22 @@
</listitem>
</itemizedlist>
<para>The Spring Framework provides first class support for integration
testing in the <filename
class="libraryfile">spring-test.jar</filename>
library (where <literal>VERSION</literal> is the release version). This
library includes the <literal>org.springframework.test</literal>
package, which contains valuable classes for integration testing with a
Spring container. This testing does not rely on an application server or
other deployment environment. Such tests are slower to run than unit
tests but much faster to than the equivalent Cactus tests or remote
tests that rely on deployment to an application server.</para>
<para>The Spring Framework provides first class support for
integration testing in
the <filename class="libraryfile">spring-test</filename> module.
The name of the actual jar file might include the the release
version and might also be in the
long <filename>org.springframework.test</filename> form,
depending on where you got it from (see
the <link linkend="dependency-management">section on Dependency
Management</link> for an explanation). This library includes
the <literal>org.springframework.test</literal> package, which
contains valuable classes for integration testing with a Spring
container. This testing does not rely on an application server
or other deployment environment. Such tests are slower to run
than unit tests but much faster to than the equivalent Cactus
tests or remote tests that rely on deployment to an application
server.</para>
<para>In Spring 2.5 and later, unit and integration testing support is
provided in the form of the annotation-driven <link