db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
Date Thu, 07 Sep 2006 14:03:23 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12433121 ] 
            
Daniel John Debrunner commented on DERBY-1522:
----------------------------------------------

The TestUtil class will not correctly report the "framework" when a JUnit test is run standalone.
It would be great to have
some shutdown database and shutdown server method in the junit classes that works from TestConfiguration.
I assume
that its location would be in TestConfiguration to match the openConnection() methods there.


For the second issue I think you can do something like this, if you had a test fixture method
called "grantTestAfterChange"

public static Suite suite() {
    // Adds all methodsthat  start with 'test 'as test fixtures
   TestSuite suite = new TestSuite(MyClass.class);

    suite.addTest(new DatabasePropertyTestSetup (new MyClass("grantTestAfterChange", props));
}

> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs
to be tested
> ----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1522
>                 URL: http://issues.apache.org/jira/browse/DERBY-1522
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.2.1.0
>            Reporter: Mamta A. Satoor
>         Assigned To: Deepa Remesh
>             Fix For: 10.2.1.0
>
>         Attachments: d1522_junit_v1.diff, d1522_junit_v1.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization
to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch
like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the
right component.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message