You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2014/06/18 06:48:05 UTC
[jira] [Commented] (DERBY-4808) write a test that checks that
optional packages are in place and clearly exposes when this is not the
case
[ https://issues.apache.org/jira/browse/DERBY-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034811#comment-14034811 ]
Myrna van Lunteren commented on DERBY-4808:
-------------------------------------------
Is there a way to check for Profile 2 (JEP 161) support?
Or will a combination of having JDBC 4.2 but no JNDI support imply this?
> write a test that checks that optional packages are in place and clearly exposes when this is not the case
> ----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4808
> URL: https://issues.apache.org/jira/browse/DERBY-4808
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-4808.diff
>
>
> Our junit tests are written in such a way that we avoid false failures because of absence of optional pieces of software.
> This is convenient when developers want to do a 'quick' test run.
> However, it's not so good when we think we're running with all optional pieces in place, but something's (gone) missing; we'll not see it and it may go unnoticed for a long time. We should get warned about missing pieces when we want *all* tests to run.
> One suggestion was to put some kind of check in the test org.apache.derbyTesting.junit.EnvTest.
--
This message was sent by Atlassian JIRA
(v6.2#6252)