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

Junjie Peng updated DERBY-3724:
-------------------------------

    Attachment: patch.txt

New patch for big.sql.
I have accepted Myrna's advices, and do some improvement.
In this patch, I also add some test cases for the parts in "big.sql" which is 
commented.
i.e. Mix clob and varchar in the table, the test case will be supported without 
 DRDAProtocolException exception is thrown. 
I also add testStringTable(), testLongVarchar() and testVarchar(). 
testStringTable() has been proved not supported yet, so I commented it again. 
For testVarchar(), When creating the table, a SQLException is thrown  with the 
prompt that 32767 is a invalid length. For testLongVarchar(),  When inserting a 
big row with the length of 33000, a SQLException is thrown  with the prompt 
that 33000 is a invalid length.  
In this situation, whether should I add testLongVarchar() and testVarchar() as 
new test cases.
I have another question: I have 10 test***() methods and 1 suite() method in 
the class of BigDataTest. When I run this test, I have seen 20 test cases run.  
What's the problem?


> Converting big.sql  to JUnit 
> -----------------------------
>
>                 Key: DERBY-3724
>                 URL: https://issues.apache.org/jira/browse/DERBY-3724
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>         Environment: windows XP Professional SP2, 
>            Reporter: Junjie Peng
>            Assignee: Junjie Peng
>             Fix For: 10.4.1.3
>
>         Attachments: patch.txt
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> It is a task of "Converting old tests to JUnit ". It request coverting  
> "derdy/java/testing/org/apache/derbyTesting/functionTests/tests/lang/big.sql" 
> into a junit. Also, it is a task of 2008 GSoc.

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

Reply via email to