db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-918) introduce a new test type to run junit tests from the current harness
Date Wed, 08 Feb 2006 19:16:57 GMT
    [ http://issues.apache.org/jira/browse/DERBY-918?page=comments#action_12365615 ] 

David Van Couvering commented on DERBY-918:
-------------------------------------------

This patch looks very good, solves the problem simply.  I agree however that granting allPermission
to junit is not the way to go, and that privileged blocks should solve this.  A nice way to
do privileged blocks is with anonymous inner classes so your test class doesn't have to implement
a "run" method that does mutiple things.


> introduce a new test type to run junit tests from the current harness
> ---------------------------------------------------------------------
>
>          Key: DERBY-918
>          URL: http://issues.apache.org/jira/browse/DERBY-918
>      Project: Derby
>         Type: Improvement
>   Components: Test
>  Environment: All
>     Reporter: Andreas Korneliussen
>     Assignee: Andreas Korneliussen
>  Attachments: DERBY-918.diff, DERBY-918.stat
>
> It seems to me that for including a new JUnit test into i.e derby-all we need to make
a new java class with a main() method, which parses a command line and set up the testsuite
and run it, just like any java program. Basically we are running the junit tests as test type
"java".
> Instead of having to do this for every junit test going into a derby test suite, I would
propose a different strategy.
> I propose to introduce a new test type called "junit" (current test types are: sql,sql2,unit,java,multi,demo
- unit is not junit)
> Then you can use:
> java org.apache.derbyTesting.functionTests.harness.RunTest <TestCaseClassName>.junit
> to run a Junit test - instead of:
> java org.apache.derbyTesting.functionTests.harness.RunTest <AnotherClassWithMainMethod>.java
> When starting a test of type junit, the RunTest class may simply use the
> junit.textui.TestRunner class, which has a main method which takes a TestCase class name
as parameter.  The junit.textui.TestRunner  runs the tests defined by the suite() method of
the TestCase class.
> I think this strategy will make it easier to integrate new JUnit tests into the current
test suites, since it save you the trouble of creating a java class with a main method for
every test.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message