Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <804042.299101285005812816.JavaMail.jira@thor>
Date: Mon, 20 Sep 2010 14:03:32 -0400 (EDT)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-4808) write a test that checks that optional
 packages are in place and clearly exposes when this is not the case
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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


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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.