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 Thu, 25 Oct 2007 09:13: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-1a.stat
                derby-3149-1a.diff

'derby-3149-1a.diff' implements the targets 'pptesting' and 'junit-pptesting'. The former
compiles the package private test, the latter runs them against the classes directories.

A new directory has been added; classes.pptesting.
The is to avoid that package private test classes are included in any of the jars, and it
might be beneficial for later extensions (i.e. package the tests in multiple separate testing
jars, merge with the other jars etc).

Note that because I couldn't find any compile classpath for Java SE 5.0, I used the one for
Java SE 6. This means that you must have specified the property jdk16 in your ant.properties
file to compile the tests.

Patch ready for review.

> 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
>
>
> 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