[ 
https://issues.apache.org/jira/browse/MUSE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531094
 ] 

Dan Jemiolo commented on MUSE-259:
----------------------------------

Very impressive set of test cases so far. One area that you haven't covered is 
muse-tools - making sure that there is no unexpected changes in the generated 
artifacts and command output is just as important as the standards compliance, 
because it can have just as big an impact on deployers. Please make sure there 
is sufficient coverage of all of the tooling scenarios (described in the 
WSDL2Java sections of the reference manual).

The test process and directory setup sounds good - my only suggestion is to 
separate all the *-test projects into /trunk/tests (sibling of /trunk/modules) 
so that people can still checkout all of the muse-* projects from /modules 
without all of the test infrastructure (could be very heavy when you consider 
the sample data). Also, in MUSE-244 you mention creating an easy-to-use unit 
test skeleton project, but it's not mentioned in this issue - I just want to 
make sure this is included because Andrew was definitely right about making it 
easier for people to contribute tests.


> Flexible test infrastructure and initial set of extensible functional tests
> ---------------------------------------------------------------------------
>
>                 Key: MUSE-259
>                 URL: https://issues.apache.org/jira/browse/MUSE-259
>             Project: Muse
>          Issue Type: Sub-task
>          Components: Other
>            Reporter: Kam K. Yee
>            Assignee: Dan Jemiolo
>             Fix For: 2.3.0
>
>         Attachments: WS-BaseNotification_1.3_TestCases_v1.0.pdf, 
> WS-DistributedManagement-MUWS1_1.1_TestCases_v1.0.pdf, 
> WS-DistributedManagement-MUWS2_1.1_TestCases_v1.0.pdf, 
> WS-MetadataExchange_TestCases_v1.0.pdf, 
> WS-ResourceFramework_1.2_Testcases_v1.0.pdf, WS-Topics_1.3_TestCases_v1.0.pdf
>
>
> Feature 244 encompases/requests multiple functionality.  This sub-task is 
> created to facilitate tracking at a more individual, granular level.  This 
> sub-task is to track the delivery of a flexible infrastructure and initial, 
> extensible suite of functional tests

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to