ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pei Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CTAKES-84) Create Regression Test Suite
Date Thu, 13 Jun 2013 16:55:20 GMT

    [ https://issues.apache.org/jira/browse/CTAKES-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682418#comment-13682418

Pei Chen commented on CTAKES-84:

The Regression Script is clever enough to run the CPE's in Aysnc and parrallel mode, however,
LVG doesn't seem work nicely with multi threading.  I've just modified so that the regression
script just runs 1 pipeline for now.

> Create Regression Test Suite
> ----------------------------
>                 Key: CTAKES-84
>                 URL: https://issues.apache.org/jira/browse/CTAKES-84
>             Project: cTAKES
>          Issue Type: Improvement
>          Components: ctakes-clinical-pipeline
>    Affects Versions: 3.0-incubating
>            Reporter: Pei Chen
>            Assignee: Pei Chen
>             Fix For: 3.1
> This may have been done manually one way or another, but I think we should establish
a standard process (pref. automated) for Regression Testing.
> Suggestion:
> - Gather all of the public test clinical notes from the various projects and put it in
the ctakes-clinical-pipeline project.
> - Write a test case that runs those notes thru the entire default pipeline and compare
it with the expected xcas.xml.
> - If there is a new module/feature, it should be expected to break the regression test.
 At that time, it should be manually verified.  After the release, the regression test expected
results should be re-recorded with the changes.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message