[
https://issues.apache.org/jira/browse/MESOS-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170308#comment-14170308
]
Niklas Quarfot Nielsen commented on MESOS-1864:
-----------------------------------------------
[~karya] Just as general JIRA practice; make sure that you have a shepherd and
that the issue is accepted before assigning yourself to the ticket.
I can help you out here, but for next time.
> Add test integration for module developers
> ------------------------------------------
>
> Key: MESOS-1864
> URL: https://issues.apache.org/jira/browse/MESOS-1864
> Project: Mesos
> Issue Type: Task
> Components: modules
> Reporter: Niklas Quarfot Nielsen
> Assignee: Kapil Arya
>
> To help module developers write and test mesos-modules, we should wire up
> integration suites that let the usual unit tests be run with custom built
> modules.
> A couple of examples could be:
> $ ./bin/mesos-tests.sh --modules="path:name"
> or a dedicated test scripts:
> $ ./bin/modules-test.sh --modules="path:name" --isolation="name"
> --authentication="name"
> We should also think about how to encourage internal module testing (tests
> that will be specific for that particular module)
> In the case of ./bin/modules-test.sh - we could run 1) our own (general)
> tests and 2) tests provided by the module it self (maybe as an extra field in
> the module registration struct)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
