[
https://issues.apache.org/jira/browse/MESOS-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191162#comment-14191162
]
Kapil Arya commented on MESOS-1864:
-----------------------------------
commit 5348496aafa9b09f2b85f84822b5b05308c6c844
Author: Kapil Arya <ka...@mesosphere.io>
Date: Thu Oct 23 18:24:32 2014 +0000
Added --modules flag for tests.
This allows the user to specify the modules to load during tests.
The modules are made available to the master and slave subsystems.
Review: https://reviews.apache.org/r/26796
> 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)
