db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3088) convert to junit, or otherwise eliminate version in tests which require an update of the master in the release management process
Date Thu, 03 Jan 2008 00:03:34 GMT

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

Myrna van Lunteren updated DERBY-3088:
--------------------------------------

    Attachment: DERBY-3088_ServerPropertiesTest2.diff

Attaching a new patch, which has all 5 tests working.

If there are no objections, I'd like to commit this.

I still need to do further recrafting of the first fixture, so it (re)uses junit classes as
Dan suggested. I'm open to further suggestions on how to approach this (in this fixture, consecutive
servers are started in a variety of mechanisms - that's what's being tested - and I find it
hard to envisage how one setup would handle this.)
The current test also still uses  noSecurityManager in one case,  (with -p) I am thinking
of modifying that to use the test's policy file.
Finally I want to see if I can figure a way to make this test run with classes - currently
you'll get a message complaining about needing derbynet.jar.
But I'd like to address these issues in a follow up patch.

> convert to junit, or otherwise eliminate version in tests which require an update of
the master in the release management process
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3088
>                 URL: https://issues.apache.org/jira/browse/DERBY-3088
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools, Test
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>         Attachments: DERBY-3088_ServerPropertiesTest.diff, DERBY-3088_ServerPropertiesTest2.diff
>
>
> There are a number of tests that require a master update every time the version number
is bumped.
> This is a tedious and error prone detail in the release management process.
> Currently affected masters are listed in tools/release/build.xml:
> java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/metadata.out
> java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/odbc_metadata.out
> java/testing/org/apache/derbyTesting/functionTests/master/metadata.out
> java/testing/org/apache/derbyTesting/functionTests/master/odbc_metadata.out
> java/testing/org/apache/derbyTesting/functionTests/master/NSinSameJVM.out
> java/testing/org/apache/derbyTesting/functionTests/master/checkToursDB.out
> java/testing/org/apache/derbyTesting/functionTests/master/testclientij.out
> java/testing/org/apache/derbyTesting/functionTests/master/testProperties.out
> It would streamline the release process if these tests in particular were either converted
to junit, or if the version numbers would be eliminated.
> Note: there already is a bug for metadata.java conversion: DERBY-2242

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


Mime
View raw message