Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <299257662.1216795711889.JavaMail.jira@brutus>
Date: Tue, 22 Jul 2008 23:48:31 -0700 (PDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3784) ImportExportTest doesn't detect lack
 of expected errors
In-Reply-To: <552493291.1216417291836.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan commented on DERBY-3784:
----------------------------------------

I applied the patch and ran the three tests. No new failures.
+1 to commit.

> ImportExportTest doesn't detect lack of expected errors
> -------------------------------------------------------
>
>                 Key: DERBY-3784
>                 URL: https://issues.apache.org/jira/browse/DERBY-3784
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.5.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: d3784.diff
>
>
> I observed that ImportExportTest contains many test cases which do try/catch/assertSQLException, but none of them call fail() at the end of the try block. Example:
> 	public void testEarlyEndOfFile() throws Exception {
> 		Connection c = getConnection();
> 		try {
> 			doImportFromFile(c, "extin/EndOfFile.txt" , "T4" , null , null , null, 0);
> 		} catch (SQLException e) {
> 			assertSQLState("XIE0E", e);
> 		}
> 	}
> I think this means that if the expected exception isn't thrown the test still passes.

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