db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3149) Add ant targets for building and running the package private tests against the classes directories
Date Fri, 09 Nov 2007 15:24:50 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan updated DERBY-3149:
-----------------------------------

    Attachment: derby-3149-1b.diff

'derby-3149-1b.diff' refreshes the patch (there was a merge conflict in build.xml) and I decided
not to run the junit-pptesting as part of junit-all/junitreport. The reason is that those
targets are capable of running against jars or classes, whereas the package-private tests
must be run against classes.

A few comments:
  * Two new targets; 'pptesting' (compile) and 'junit-pptesting' (run).
  * Compile target 'pptesting' is included in target 'all'.
  * Compile target 'pptesting' is not included in target 'testing'.
  * Class files are put into 'classes.pptesting'.

Currently there are 94 tests, and they take around 6 seconds to run on my machine.

> Add ant targets for building and running the package private tests against the classes
directories
> --------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3149
>                 URL: https://issues.apache.org/jira/browse/DERBY-3149
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Build tools, Test
>    Affects Versions: 10.4.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>         Attachments: derby-3149-1a.diff, derby-3149-1a.stat, derby-3149-1b.diff
>
>
> Create ant targets in build.xml to compile and run the package private tests.
> The first step will be to run the tests against the classes directories. Implementing
a solution that runs against jars is not technically difficult, it just brings a host of decisions
to be taken... Maybe even more important, does running against the jars add any value?
> The compile will be included in the 'all' target to test the implementation. Feel free
to post your concerns if you think building the package private tests should be a manual action
only.
> The tests will also be run as part of junit-all / junitreport.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message