db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3204) Regression tests for demos included in releases
Date Fri, 16 Nov 2007 10:01:43 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543022
] 

John H. Embretsen commented on DERBY-3204:
------------------------------------------

I just realized that there actually is a test for the "simple" demo, SimpleApp.java. That
is, the simple demo is run as a separate test as part of the following suites in the old harness:

         * simpledemo
      * demo
   * derbyall

SimpleApp.class is included in derbyTesting.jar.

Running the test with -Dframework=DerbyNetClient still runs it in embedded mode. I think this
is because the demo requires the argument "derbyclient" for it to use the client driver, and
no arguments are sent from the test harness. Also, the test classpath probably includes more
than what is specified in the demo instructions. As part of derbyall, the demo suite only
runs in the embedded framework. All this prevented the DERBY-3187 simple demo client regression
in 10.3.1.4 from being detected by derbyall runs.

The checkToursDB.java test is also part of the demo suite, run as part of derbyall (embedded).
This test only supports the embedded framework. The toursdb demo's sql files are included
in derbyTesting.jar.

> Regression tests for demos included in releases
> -----------------------------------------------
>
>                 Key: DERBY-3204
>                 URL: https://issues.apache.org/jira/browse/DERBY-3204
>             Project: Derby
>          Issue Type: Improvement
>          Components: Demos/Scripts, Test
>    Affects Versions: 10.3.1.4
>            Reporter: John H. Embretsen
>
> Several demos are included in Derby's -bin distributions, but there are almost no tests
in place to verify that these demos still work as expected, or that they work at all. There
should be (JUnit?) tests in place testing at least some of these demos in their intended environments.
These tests should be run at regular intervals, for example as part of the release process,
or as part of the regular regression test suites.
> In -bin distributions, various demo programs are located in the directory demo/programs/.
For the next feature release this currently includes:
>    * localcal
>    * nserverdemo
>    * scores
>    * simple
>    * toursdb
>    * vtis
>    * workingwithderby
> DERBY-3190 adds yet another demo, simplemobile.
> There is currently one demo test in java/testing/org/apache/derbyTesting/functionTests/tests/demo/,
called checkToursDB.java (old harness).

-- 
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