1. 11 7月, 2016 1 次提交
  2. 20 12月, 2015 1 次提交
  3. 29 9月, 2015 2 次提交
    • J
      Polishing · a9fbbc55
      Juergen Hoeller 提交于
      a9fbbc55
    • S
      Throw meaningful exception if JUnit 4.9 is not present · d883efcb
      Sam Brannen 提交于
      SpringJUnit4ClassRunner, SpringClassRule, and SpringMethodRule now
      throw an IllegalStateException with a meaningful message if JUnit 4.9
      is not present in the classpath (specifically if
      org.junit.runners.model.MultipleFailureException cannot be loaded).
      
      Issue: SPR-13521
      d883efcb
  4. 18 5月, 2015 2 次提交
  5. 17 5月, 2015 2 次提交
    • S
      Introduce TestContextManager cache in SpringClassRule · 973582e7
      Sam Brannen 提交于
      In order to simplify configuration of the SpringMethodRule and to ensure
      that the correct TestContextManager is always retrieved for the
      currently executing test class, this commit introduces a static
      TestContextManager cache in SpringClassRule.
      
      In addition, since it is not foreseen that SpringClassRule and
      SpringMethodRule should be able to be subclassed, their internal methods
      are now private instead of protected.
      
      Issue: SPR-7731
      973582e7
    • S
      Introduce JUnit Rule alternative to SpringJUnit4ClassRunner · d1b1c4f8
      Sam Brannen 提交于
      Since Spring Framework 2.5, support for integrating the Spring
      TestContext Framework (TCF) into JUnit 4 based tests has been provided
      via the SpringJUnit4ClassRunner, but this approach precludes the
      ability for tests to be run with alternative runners like JUnit's
      Parameterized or third-party runners such as the MockitoJUnitRunner.
      
      This commit remedies this situation by introducing @ClassRule and @Rule
      based alternatives to the SpringJUnit4ClassRunner. These rules are
      independent of any Runner and can therefore be combined with
      alternative runners.
      
      Due to the limitations of JUnit's implementation of rules, as of JUnit
      4.12 it is currently impossible to create a single rule that can be
      applied both at the class level and at the method level (with access to
      the test instance). Consequently, this commit introduces the following
      two rules that must be used together.
      
       - SpringClassRule: a JUnit TestRule that provides the class-level
         functionality of the TCF to JUnit-based tests
      
       - SpringMethodRule: a JUnit MethodRule that provides the
         instance-level and method-level functionality of the TCF to
         JUnit-based tests
      
      In addition, this commit also introduces the following new JUnit
      Statements for use with rules:
      
       - RunPrepareTestInstanceCallbacks
      
       - ProfileValueChecker
      
      Issue: SPR-7731
      d1b1c4f8