db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5656) Bring master based unit tests T_* into Suites.All
Date Wed, 14 Mar 2012 23:18:40 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229745#comment-13229745

Mike Matrigali commented on DERBY-5656:

I think this is a good step.  Some of the tricky store code cases are tested only now in these
unit tests.

It would be also nice if at same time at least one test was added that did assertion based
testing at this level that could be used as a model
for subsequent work, either for converting the existing module tests or writing new ones.
 If at all possible I would rather see sql based testing,
but sometimes unit testing is easier.  For history some of this unit testing was the only
way that tests could be written at the time as the
SQL functionality to call the routines did not exist.  
> Bring master based unit tests  T_* into Suites.All
> --------------------------------------------------
>                 Key: DERBY-5656
>                 URL: https://issues.apache.org/jira/browse/DERBY-5656
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions:
>            Reporter: Kathey Marsden
> The unit tests under derbyTesting/unitTests that start with T_ , e.g store/T_AccessFactory.java
along with the property files under derbyTesting/functionTests/tests/unit are master based
java  tests with some magic to get the module to load etc.
> It would be good to have a way to pull these into suites.All just keeping them as master
based tests.  Something like or supplemental to HarnessJavaTest .
> I don't think for these tests it is worthwhile to go through each one and try to actually
do assertion based assertions as I think such a task would be very  error prone and difficult
to understand the intentions of the authors, but it would be great to get them out of the
harness and into suites.All.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message