[
https://issues.apache.org/jira/browse/MUSE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521158
]
Kam K. Yee commented on MUSE-259:
---------------------------------
======================================
PROPOSED IMPLEMENTATION - HIGH LEVEL
======================================
Following are some initial thoughts/proposal for the implementation of the
various tests and framework. (This proposal incorporates and adds to the input
from Andrew Eberbach's previous postings and email exchanges (Thanks! Andrew).
- The unit, functional, and stress tests will be JUnit based.
- ANT scripts will be created to setup and invoke these JUnit test suites.
FUNCTIONAL TESTING:
- This would loosely follow Dan's current approach of top-level directories
that are related to specific capabilties (wsrf, wsn, etc). The structure here
isn't as easy to generalize, but some directory/hierarchical organization that
seems sane would suffice. Again, the goal here is self-containment as to avoid
an overly complex test environment.
- A new target will be introduced to the build.xml to build a new archive
(muse-test-fvt-bin) containing only the functional test code and needed
artifacts (e.g., WSDLs & XSDs).
- The identified steps for functional testing are as follows:
1. Download or locally build muse-bin runtime archive
2. Download or locally build muse-test-fvt-bin archive
3. Unzip muse-bin
4. Unzip muse-test-fvt-bin
5. Run muse-bin code generation tool to generate endpoint(s) to be deployed
to target container
6. Deploy generated endpoint(s) to the target container
7. Startup target container with generated endpoint(s)
8. Invoke execution of JUnit functional test suites
- A new functional test ANT script will be created to invoke and execute the
different JUnit test suites.
Later on when full automation is introduced, the automation framework will be
invoking these ANT script target to automatically execute the test suites.
- This design also allows for developers to do a sanity check by running these
tests locally on their machines prior to checking code into the repository.
Finally, since modifying something simple is usually easier than generating
something simple from scratch, we will create two "read only" top-level
directories which would lay out a reasonable skeleton for users contributing
their own junit and functional tests for top-level directories.
> 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
>
>
> 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]
