Hi Jayaradha,

First of all, Welcome to the Apex-Dev community!

Happy to see that you want to contribute to testing down the line. I'll
talk about the "*testing part*" and others in the community can comment on
the process for release management/automation.

To start with you can have a look at
http://apex.incubator.apache.org/docs/apex-3.3/ for making yourself
familiar with the Apex. If you have done so already, please visit these
docs to understand more on testing:

Apache Apex Development Environment Setup
<http://apex.incubator.apache.org/docs/apex-3.3/apex_development_setup/#apache-apex-development-environment-setup>
​Testing
<http://apex.incubator.apache.org/docs/apex-3.3/application_development/#testing>
​
Testing your Operator
<http://apex.incubator.apache.org/docs/apex-3.3/operator_development/#testing-your-operator>

​CLI commands <http://apex.incubator.apache.org/docs/apex-3.3/dtcli/>​


​Currently apex has junit tests in place for each operator in Apex Malhar
library
<http://apex.incubator.apache.org/docs/apex-3.3/operator_development/#malhar-operator-library>.
You can extend those tests and submit to the corresponding repository.

On the other hand, if you want to test the overall apex platform without
writing/using junit tests, there is a command-line utility
<http://apex.incubator.apache.org/docs/apex-3.3/dtcli/> (named as "dtcli";
soon will be renamed to "apex") which is used to handle all the operations
(e.g. launch, kill-app, list-operators etc.) for an apex application. You
can get your hands on this utility and test the platform by automating
testcases for the commands.

If you have any more ideas on testing/automation, please share with us.

p.s. For more information on documentation, you can visit this link
<http://docs.datatorrent.com/> as the Apex documentation is currently in
process of migrating from this site.


On Wed, Mar 9, 2016 at 3:35 AM, Jayaradha Natarajan <[email protected]>
wrote:

> I am Jayaradha. I would like to contribute to Apache Apex release
> management, release automation and testing to start with. Eventually I will
> start contributing to development.  Please let me know the steps to
> contribute to Release management and testing.
>
> Thanks,
> Jayaradha
>



-- 
*regards,*
*~pradeep*

Reply via email to