[
https://issues.apache.org/jira/browse/MADLIB-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540497#comment-16540497
]
ASF GitHub Bot commented on MADLIB-1252:
----------------------------------------
GitHub user njayaram2 opened a pull request:
https://github.com/apache/madlib/pull/290
madpack: Add madpack option to run unit tests.
JIRA: MADLIB-1252
Unit tests in MADlib are written in python files, that are located in
the ...<module_name>/test/unit_tests/ folders, whose names begin with
the prefix "test_". This commit adds a new madpack option to run unit
tests similar to how we run install and dev checks.
- The new option added is: `unit-test`.
- Sample usage (on a postgres database, with MADlib installed on
database `madlib`):
* Run unit tests on all modules that have it defined:
src/bin/madpack -p postgres -c /madlib unit-test
* Run unit tests only for the `convex` module:
src/bin/madpack -p postgres -c /madlib unit-test -t convex
* Run unit tests only for the `convex` and decision trees module:
src/bin/madpack -p postgres -c /madlib unit-test -t
convex,recursive_partitioning/decision_tree
- Add command to run all unit tests in Jenkins build script.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/madlib/madlib madpack/unit-test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/madlib/pull/290.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #290
----
commit 5f4395bc8548a5f74ba9a8fcb716f2a39ec51162
Author: Nandish Jayaram <njayaram@...>
Date: 2018-07-11T00:32:24Z
madpack: Add madpack option to run unit tests.
JIRA: MADLIB-1252
Unit tests in MADlib are written in python files, that are located in
the ...<module_name>/test/unit_tests/ folders, whose names begin with
the prefix "test_". This commit adds a new madpack option to run unit
tests similar to how we run install and dev checks.
- The new option added is: `unit-test`.
- Sample usage (on a postgres database, with MADlib installed on
database `madlib`):
* Run unit tests on all modules that have it defined:
src/bin/madpack -p postgres -c /madlib unit-test
* Run unit tests only for the `convex` module:
src/bin/madpack -p postgres -c /madlib unit-test -t convex
* Run unit tests only for the `convex` and decision trees module:
src/bin/madpack -p postgres -c /madlib unit-test -t
convex,recursive_partitioning/decision_tree
- Add command to run all unit tests in Jenkins build script.
----
> Add option to run unit tests in madpack
> ---------------------------------------
>
> Key: MADLIB-1252
> URL: https://issues.apache.org/jira/browse/MADLIB-1252
> Project: Apache MADlib
> Issue Type: Improvement
> Components: Madpack
> Reporter: Nandish Jayaram
> Assignee: Nandish Jayaram
> Priority: Major
>
> We have been able to run install check and dev check on all or specific
> modules using the `install-check` and `dev-check` madpack options. Can we
> have an option called `unit-test` to be able to run unit tests on all or
> specific modules?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
